February 2016 - Pharo-dev - lists.pharo.org

Smalltalkhub scheduled maintenance today (February, 22nd)

by Christophe Demarey

Hello, Smalltalk will be down today (february, 22nd) from 12:30 to 13:30 (french local time). IT will add storage to the root partition (last maintenance finally did not take place). Regards, Christophe

Feb. 22, 2016

Re: [Pharo-dev] Yet again, wrong tempvars in debuggers context variables list

by Guille Polito

Hmm, I know that the Spur bootstrap does a lot of changes "in the background". For example, it replaces literals in methods (Float->BoxedFloat64), plus it inlines all immediate characters. I do not know if it is related, but this could be a side effect, and it would explain why there is no evident change causing this. On 02/22/2016 09:08 AM, Nicolai Hess wrote: > > > 2016-02-20 20:31 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>>: > > > > 2016-02-20 19:11 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>>: > > This is not an issue with GTDebugger, but the way opal > generates the tempvar > index or the way, debuggerMap tries to access the context vars > > 17660 > <https://pharo.fogbugz.com/f/cases/17660/wrong-tempvar-values-in-debugger> > wrong tempvar values in debugger > > > This is a really special case, I wasn't able yet to create an > easier example for reproducing this bug: > - put a self haltOnce in > RAbstractClass>>#directlyDefinesLocalMethod: > - enable halt once > - select any other method in Nautilus and choose > "Rename method (all)" from method panes context menu > - enter a new name and push "OK" > -> the debugger pops up in method > directlyDefinesLocalMethod: > - select the first "allClassesDo:" context from top of the stack > -> the debugger shows that we are in the evalBlock context > The "seen" variable is a Set, but if you look at the > "Variables"-pane, it is shown > as a block (this is actually the parameter aBlock) > > > again, this is caused by a change for spur migration > > This worked up to pharo 50496 > starting with pharo 50497, the order of variables has changed. > > see > http://forum.world.st/pharo-project-pharo-core-dfd4f3-50497-td4867046.html > <https://pharo.fogbugz.com/f/cases/17241/ffi-nb-is-not-cleaning-compiled-met…> > > > Any idea what has changed? > I could not spot a change that could be responsible for this. > The order of tempvars in a block context somehow changed, and the way > the debugger accesses the temps > by name (get an index and access the context temp vars by index) > somehow changed. > Recompiling the affected methods helps, but I would like to know if > this change (where is it?) was on purpose. >

Feb. 22, 2016

Re: [Pharo-dev] preferred way to invoke debugger

by Denis Kudriashov

Hi. Now you should first create DebugSession: debugSession := Processor activeProcess newDebugSessionNamed: 'Code simulation error' startedAt: self. Smalltalk tools debugger openOn: debugSession withFullView: true. 2016-02-21 4:34 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > What is the replacement for...? > [ Smalltalk tools debugger > openContext: self > label:'Code simulation error' > contents: nil]. > > In adding support to simulate new OwnedLock primitives, I see this is sent > from > Context>>doPrimitive:method:receiver:args: > but this is no longer in the image. I can update it as I go. > > cheers -ben > >

Feb. 22, 2016

Re: [Pharo-dev] Why the GTSpotter help does not explain all the categories

by Tudor Girba

Hi, Indeed, this is a problem: https://pharo.fogbugz.com/f/cases/17668/Spotter-should-allow-filtering-cate… Now, I enhanced the category matching to ignore the whitespace. So, now you can say: #Classinstancevariables Another option would be to change the names of categories to have underscore instead of space. Like this: #Class_instance_variables What do you think? Cheers, Doru > On Feb 21, 2016, at 7:22 PM, stepharo <stepharo(a)free.fr> wrote: > > Thanks but it does not really help understanding. At least I do not get it at all. > > I have no idea how from > > Class instance variables > > I should type something meaningfull. > > > I could get it for Examples, Implementors, Senders because there is only one word. > > > > > Le 20/2/16 14:34, Tudor Girba a Ã©crit : >> We added the mechanism and created a kind of an API entry for documenting all entries within the image. This was one of your request: to know what are all the different searches possible :). >> >> Doru >> >> >>> On Feb 20, 2016, at 2:26 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> So I tried again to understand how spotter works and I looked at the help and I could not understand >>> how I can find class references. >>> >>> I saw that but it does not show me how I can use it and I do not really want to understand how this is implemented. >>> >>> spotterReferenceFor: aStep >>> <spotterOrder: 30> >>> aStep listProcessor >>> title: 'References'; >>> allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; >>> itemName: [ :method | method gtDisplayString ]; >>> filter: GTFilterSubstring >>> >>> >>> >>> To me this help is totally obscure. >>> >>> >>> Spotter allows the developer to define custom search processors in different classes. These custom processors take effect when Spotter reaches an instance of the extended class. You can find below the list of extensions from this image. >>> >>> You can also browse this list by inspecting: >>> >>> GTSpotter spotterExtendingMethods >>> >>> Behavior >>> - Class instance variables (spotterClassInstanceVariablesFor:) >>> - Composing traits (spotterCompositionFor:) >>> - Instance variables (spotterInstanceVariablesFor:) >>> - QA Critics (spotterQACriticsFor:) >>> - All subclasses (spotterSubclassesFor:) >>> - All superclasses (spotterSuperclassesFor:) >>> - Users (spotterTraitUsersFor:) >>> - Special Slots (spotterUsedSlotsFor:) >>> - Uses Traits (spotterUsedTraitsFor:) >>> >>> Class >>> - Examples (gtSpotterGTExamplesFor:) >>> - Class methods (spotterClassMethodsFor:) >>> - Instance methods (spotterMethodsFor:) >>> - References (spotterReferenceFor:) >>> - Super class methods (spotterSuperClassMethodsFor:) >>> - Super instance methods (spotterSuperMethodsFor:) >>> >>> ClassDescription >>> - Package (spotterPackageFor:) >>> >>> Collection >>> - spotterItemsFor: (spotterItemsFor:) >>> >>> CompiledMethod >>> - Bytecode (spotterForBytecodesFor:) >>> - Implementors (spotterForImplementorsFor:) >>> - Senders (spotterForSendersFor:) >>> - Class (spotterMethodClassFor:) >>> - QA Critics (spotterQACriticsFor:) >>> >>> Dictionary >>> - Keys (spotterForKeysFor:) >>> >>> FileReference >>> - Directories (spotterForDirectoriesFor:) >>> - Files (spotterForFilesFor:) >>> - Directories (spotterForZipDirectoriesFor:) >>> - Files (spotterForZipFilesFor:) >>> >>> GTExample >>> - Example Dependencies (gtSpotterDependenciesFor:) >>> - Example Dependents (gtSpotterDependentsFor:) >>> - Example Provider (gtSpotterProviderFor:) >>> - Example Source (gtSpotterSourceFor:) >>> - Example Subjects (gtSpotterSubjectsFor:) >>> >>> GTExampleFinder >>> - Examples (gtSpotterExamplesFor:) >>> >>> GTExampleFinder class >>> - Examples (gtSpotterExamplesFor:) >>> >>> GTExampleOrganizer >>> - Examples (gtSpotterGTExamplesFor:) >>> >>> GTExampleProxy >>> - Example Dependencies (gtSpotterDependenciesFor:) >>> - Example Dependents (gtSpotterDependentsFor:) >>> >>> GTInspector class >>> - Extensions (spotterExtensionsFor:) >>> >>> GTSelectorImplementors >>> - Implementors (spotterImplementorsFor:) >>> - Senders (spotterSendersFor:) >>> >>> GTSpotter >>> - Examples (gtSpotterExamplesFor:) >>> - Catalog Projects (spotterCatalogProjectsFor:) >>> - Clipboard History (spotterClipboardFor:) >>> - Methods (spotterConcreteMethodFor:) >>> - Dirty Monticello packages (spotterDirtyMonticelloPackagesFor:) >>> - Playground cached pages (spotterForCachedPlaygroundPagesFor:) >>> - Classes (spotterForClassesFor:) >>> - Directories (spotterForDirectoriesFor:) >>> - Calculator (spotterForExpressionsFor:) >>> - Files (spotterForFilesFor:) >>> - Global variables (spotterForGlobalVarsFor:) >>> - Help topics (spotterForHelpTopicFor:) >>> - Messages (spotterForMessagesFor:) >>> - Metacello Configurations (spotterForMetacelloConfigurationsFor:) >>> - Packages (spotterForPackagesFor:) >>> - Pragmas (spotterForPragmasFor:) >>> - References (spotterForReferencesFor:) >>> - Monticello Repositories (spotterForRepositoriesFor:) >>> - Senders (spotterForSendersFor:) >>> - spotterForStashedPlaygroundPagesFor: (spotterForStashedPlaygroundPagesFor:) >>> - History (spotterHistoryFor:) >>> - Implementors (spotterImplementorsFor:) >>> - ws.stfx.eu (spotterStfxFor:) >>> - Menu (spotterWorldMenuFor:) >>> >>> GTSpotter class >>> - Extensions (spotterExtensionsFor:) >>> >>> GTSpotterExceptionMock1 >>> - mockProcessorFor: (mockProcessorFor:) >>> >>> GTSpotterExceptionMock2 >>> - mockProcessorFor: (mockProcessorFor:) >>> >>> GTSpotterExceptionMock3 >>> - mockProcessorFor: (mockProcessorFor:) >>> >>> GTSpotterExceptionMock4 >>> - mockProcessorFor: (mockProcessorFor:) >>> >>> GTSpotterExceptionMock5 >>> - mockProcessorFor: (mockProcessorFor:) >>> >>> GlobalVariable >>> - Class (spotterClassFor:) >>> - References (spotterForReferencesFor:) >>> >>> HelpTopic >>> - Help contents (spotterForHelpTopicFor:) >>> >>> KMDispatcher >>> - Keys (spotterForKeysFor:) >>> >>> MCPackage >>> - Packages (spotterForPackageFor:) >>> - Monticello Working Copy (spotterMonticelloWorkingCopyFor:) >>> >>> MCVersionInfo >>> - Ancestors (spotterAncestorsFor:) >>> >>> MCWorkingCopy >>> - All other repositories (spotterAllRepositoriesFor:) >>> - Ancestors (spotterAncestorsFor:) >>> - Monticello Package (spotterMonticelloPackageFor:) >>> - Packages (spotterPackageFor:) >>> - Package repositories (spotterPackageRepositoriesFor:) >>> >>> MenuItemMorph >>> - spotterItemsFor: (spotterItemsFor:) >>> >>> MenuMorph >>> - Items (spotterItemsFor:) >>> >>> MetacelloAbstractPackageSpec >>> - Includes (spotterForIncludesFor:) >>> - Requires (spotterForRequiresFor:) >>> >>> MetacelloProject >>> - Versions (spotterForVersionsFor:) >>> >>> MetacelloVersion >>> - Groups (spotterForGroupsFor:) >>> - Packages (spotterForPackagesFor:) >>> >>> Morph >>> - spotterForKeysFor: (spotterForKeysFor:) >>> - Submorphs (spotterForSubmorphsFor:) >>> >>> PragmaType >>> - Pragmas (spotterPragmasFor:) >>> - Senders (spotterSendersFor:) >>> >>> RPackage >>> - Classes (spotterClassesFor:) >>> - Extension Methods (spotterExtensionMethodsFor:) >>> - Monticello Package (spotterMonticelloPackageFor:) >>> - Monticello Working Copy (spotterMonticelloWorkingCopyFor:) >>> - Tags (spotterTagsFor:) >>> >>> RPackageTag >>> - Classes (spotterClassesFor:) >>> >>> SettingNode >>> - Children (spotterForSettingsFor:) >>> >>> SettingTree >>> - Settings (spotterForSettingsFor:) >>> >>> Slot >>> - Accesses (spotterAccessesFor:) >>> >>> Trait >>> - Examples (gtSpotterGTExamplesFor:) >>> - Class methods (spotterClassMethodsFor:) >>> - Instance methods (spotterMethodsFor:) >>> - References (spotterReferenceFor:) >>> - Super class methods (spotterSuperClassMethodsFor:) >>> - Super instance methods (spotterSuperMethodsFor:) >>> >>> TraitBehavior >>> - Class instance variables (spotterClassInstanceVariablesFor:) >>> - Composing traits (spotterCompositionFor:) >>> - Instance variables (spotterInstanceVariablesFor:) >>> - QA Critics (spotterQACriticsFor:) >>> - All subclasses (spotterSubclassesFor:) >>> - All superclasses (spotterSuperclassesFor:) >>> - Users (spotterTraitUsersFor:) >>> - Special Slots (spotterUsedSlotsFor:) >>> - Uses Traits (spotterUsedTraitsFor:) >>> >>> TraitDescription >>> - Package (spotterPackageFor:) >>> >>> >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Reasonable is what we are accustomed with." >> >> >> > > -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Feb. 22, 2016

Re: [Pharo-dev] double selection in the debugger is confusing

by Nicolai Hess

2016-02-21 19:19 GMT+01:00 stepharo <stepharo(a)free.fr>: > Here this is terribly confusing because we could think that the execution > will go inside > the true block but no in reality it is jumping right after. > So we must remove this selection of matching terms. > This was always like that, but with rubric, the "second selection" highlight is much more visible. In older non-rubric text handling, the second selection was just a pale light color, without border. Maybe we should remove the border for rubrics "second selection" text highlight. > > Stef > > Le 21/2/16 19:04, stepharo a Ã©crit : > > Hi guy >> >> we should disable the double selection when we click on a stack element >> because we get selection in frame and in fill and this is confusing >> because the PC is represented by the filled >> one. >> >> Stef >> > > >

Feb. 22, 2016

Re: [Pharo-dev] cannot use shortcut in text pane of MC

by Guille Polito

Can you load the slice and test ? :D On 02/22/2016 08:41 AM, Marcus Denker wrote: > https://pharo.fogbugz.com/f/cases/17570/Shortcuts-to-browse-code-are-not-av… > > There are *lots* of fixes in the queue to be integratedâ¦ progress is slow sometimes (e.g. this was done 12 days > ago but we have just yesterday found someone to review to the fix). > > Marcus > >> On 21 Feb 2016, at 18:52, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guillermo >> >> I do not know if this is the one you fixed but in >> Pharo5.0 >> Latest update: #50596 >> >> I cannot type the name of class and browse it in a MC textpane. >> >> Stef >> <Screen Shot 2016-02-21 at 18.52.01.png> >

Feb. 22, 2016

Re: [Pharo-dev] Yet again, wrong tempvars in debuggers context variables list

by Nicolai Hess

2016-02-20 20:31 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-02-20 19:11 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> This is not an issue with GTDebugger, but the way opal generates the >> tempvar >> index or the way, debuggerMap tries to access the context vars >> >> 17660 >> <https://pharo.fogbugz.com/f/cases/17660/wrong-tempvar-values-in-debugger> >> wrong tempvar values in debugger >> >> >> This is a really special case, I wasn't able yet to create an easier >> example for reproducing this bug: >> - put a self haltOnce in >> RAbstractClass>>#directlyDefinesLocalMethod: >> - enable halt once >> - select any other method in Nautilus and choose >> "Rename method (all)" from method panes context menu >> - enter a new name and push "OK" >> -> the debugger pops up in method >> directlyDefinesLocalMethod: >> - select the first "allClassesDo:" context from top of the stack >> -> the debugger shows that we are in the evalBlock context >> The "seen" variable is a Set, but if you look at the "Variables"-pane, it >> is shown >> as a block (this is actually the parameter aBlock) >> > > again, this is caused by a change for spur migration > > This worked up to pharo 50496 > starting with pharo 50497, the order of variables has changed. > > see > http://forum.world.st/pharo-project-pharo-core-dfd4f3-50497-td4867046.html > <https://pharo.fogbugz.com/f/cases/17241/ffi-nb-is-not-cleaning-compiled-met…> > > Any idea what has changed? I could not spot a change that could be responsible for this. The order of tempvars in a block context somehow changed, and the way the debugger accesses the temps by name (get an index and access the context temp vars by index) somehow changed. Recompiling the affected methods helps, but I would like to know if this change (where is it?) was on purpose.

Feb. 22, 2016

Re: [Pharo-dev] in 50596 protocol icons are lost

by Marcus Denker

https://pharo.fogbugz.com/f/cases/17524/Invisible-protocol-icons no fix yet > On 21 Feb 2016, at 19:00, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > I noticed that when I look at the protocols with > > Pharo5.0 > Latest update: #50596 > > that the icons are damaged. > > Stef > <Screen Shot 2016-02-21 at 18.59.10.png>

Feb. 22, 2016

Re: [Pharo-dev] cannot use shortcut in text pane of MC

by Marcus Denker

https://pharo.fogbugz.com/f/cases/17570/Shortcuts-to-browse-code-are-not-av… There are *lots* of fixes in the queue to be integratedâ¦ progress is slow sometimes (e.g. this was done 12 days ago but we have just yesterday found someone to review to the fix). Marcus > On 21 Feb 2016, at 18:52, stepharo <stepharo(a)free.fr> wrote: > > Hi guillermo > > I do not know if this is the one you fixed but in > Pharo5.0 > Latest update: #50596 > > I cannot type the name of class and browse it in a MC textpane. > > Stef > <Screen Shot 2016-02-21 at 18.52.01.png>

Feb. 22, 2016

Re: [Pharo-dev] How was BoxedFloat64 integrated into the image ?

by wernerk

Beware, most client code should only refer to the visible faÃ§ade Float and its API. BoxedFloat64 is an implementation detail and is VM dependent. We don't want client code to be VM dependent, do we? I hope those references to BoxedFloat64 are rare. Hi Nicolas, Of course i agree that making client code dependent on the vm is a bad idea and generally i agree with everything you said. but i do have some experience with using BoxedFloat64 and this experience showed me that relying simply on Float occasionaly just is not posssible (that 'implementation detail' does have an effect on one of my programs). i for one would appreciate it, if BoxedFloat64 would _not_ be hidden behind Float in the source code. werner -- View this message in context: http://forum.world.st/How-was-BoxedFloat64-integrated-into-the-image-tp4878… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 21, 2016