- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50562 Home: https://github.com/pharo-project/pharo-core

Feb. 2, 2016

[pharo-project/pharo-core] 0f7198: 50562

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0f71987906596fff89e93063d9ac08c9c2d6815c https://github.com/pharo-project/pharo-core/commit/0f71987906596fff89e93063… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-02 (Tue, 02 Feb 2016) Changed paths: M Kernel-Tests.package/ProcessTest.class/instance/testing/testFork.st R Kernel-Tests.package/ProcessTest.class/instance/testing/testHighPriorityOverridesWaitTime.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testSchedulingHigherPriorityServedFirst.st R Kernel-Tests.package/ProcessTest.class/instance/testing/testSchedulingIsFirstComeFirstServed.st A Kernel-Tests.package/ProcessTest.class/instance/testing/testSchedulingSamePriorityFirstComeFirstServed.st M Multilingual-Languages.package/LanguageEnvironment.class/class/initialization/initialize.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50561.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50562.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50561.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50562.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/FastTableModel.class/README.md A Spec-Core.package/FastTableModel.class/class/example/example.st A Spec-Core.package/FastTableModel.class/class/specs/adapterName.st A Spec-Core.package/FastTableModel.class/class/specs/defaultSpec.st A Spec-Core.package/FastTableModel.class/definition.st A Spec-Core.package/FastTableModel.class/instance/api-events/whenIconsChanged_.st A Spec-Core.package/FastTableModel.class/instance/api/doubleClickAction.st A Spec-Core.package/FastTableModel.class/instance/api/doubleClickAction_.st A Spec-Core.package/FastTableModel.class/instance/api/doubleClick_.st A Spec-Core.package/FastTableModel.class/instance/api/getIconFor_.st A Spec-Core.package/FastTableModel.class/instance/api/handlesDoubleClick.st A Spec-Core.package/FastTableModel.class/instance/api/handlesDoubleClick_.st A Spec-Core.package/FastTableModel.class/instance/api/icons.st A Spec-Core.package/FastTableModel.class/instance/api/icons_.st A Spec-Core.package/FastTableModel.class/instance/as yet unclassified/registerEvents.st A Spec-Core.package/FastTableModel.class/instance/as yet unclassified/wrapItem_.st A Spec-Core.package/FastTableModel.class/instance/initialization/initializeValueHolders.st M Spec-Core.package/ListModel.class/instance/initialization/initialize.st A Spec-Core.package/ListModel.class/instance/initialization/initializeValueHolders.st M Spec-Core.package/SpecAdapterBindings.class/instance/initialize/initializeBindings.st M Spec-MorphicAdapters.package/MorphicAdapterBindings.class/instance/initialize/initializeBindings.st A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/README.md A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/definition.st A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/instance/as yet unclassified/doubleClick_.st A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/instance/as yet unclassified/wrapItem_.st A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/instance/factory/buildWidget.st A Spec-MorphicAdapters.package/MorphicFastTableAdapter.class/instance/widget API/getIconFor_.st M System-Support.package/SystemDictionary.class/instance/classes and traits/forgetClass_logged_.st Log Message: ----------- 50562 17515 fix minimal Pharo shrinking build https://pharo.fogbugz.com/f/cases/17515 17512 Spec should use FastTable https://pharo.fogbugz.com/f/cases/17512 17501 ProcessTest>>testHighPriorityOverridesWaitTime intermittent failures https://pharo.fogbugz.com/f/cases/17501 17035 The smallSaveIcon is the same as the smallSaveAsIcon https://pharo.fogbugz.com/f/cases/17035 http://files.pharo.org/image/50/50562.zip

Feb. 2, 2016

GTInspector and PointerExplorer

by Nicolai Hess

Anyone working with GTInspector and inspecting "pointers to" (menu Item "Open pointers to"). Either I make something wrong or it just does not work. The only references I can see in this pointer inspector are the references *from* the inspector itself. I put an EllipseMorph in a Morph and choosed "Open Pointers to" in the inspector of the EllipseMorph. I would expect something like EllipseMorph <- array (submorphs) <- Morph But instead I only see this:

Feb. 2, 2016

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

by Eliot Miranda

Hi Stef, > On Feb 1, 2016, at 11:03 PM, stepharo <stepharo(a)free.fr> wrote: > > What about something like that > > > My instances hold 64-bit Floats in heap objects. This is the only representation on 32-bit systems. But on 64-bit systems SmallFloat64 holds a subset of the full 64-bit double-precision range in immediate objects. > > BoxedFloat64 is the classical VM Float, two 4-bytes word allocated per Float, and is both for 32 bits VM and Float values not fitting in immediate format. This is because 3 bits have been removed from the exponent due to the object internal representation needed for the Spur new garbage collector. > > So on a 32 bits VM Floats are represented either by BoxedFloat64 or Float. No. Float is now an abstract class. There are only instances of BoxedFloat64 or SmallFloat64. And in 32-bits there are only BoxedFloat64 instances. So on a 32 bits VM Floats are represented only by BoxedFloat64. On a 64 bits VM Floats are represented either by BoxedFloat64 or SmallFloat64. > >

Feb. 2, 2016

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

by Eliot Miranda

Stef, in 32-bit Spur there are only BoxedFloat64 instances. In 64-bit Spur there are (already) both BoxedFloat64 instances and SmallFloat64 immediates. In 64-but Spur, if a float's exponent is in the middle 8 bit range of the 11-bit double precision exponent range it is represented as a SmallFloat64 immediate and occupies no space except the slot referencing it, just as with SmallInteger. There is good documentation of the scheme in VMMaker.oscog. When time allows I'll write more informative class comments, but look at the SmallInteger comment, that's not detailed either. _,,,^..^,,,_ (phone) > On Feb 1, 2016, at 11:00 PM, stepharo <stepharo(a)free.fr> wrote: > > Tx nicolas > > I read > > SmallFloat64: My instances represent 64-bit Floats whose exponent fits in 8 bits as immediate objects. This representation is only available on 64-bit systems, not 32-bit systems. > > BoxedFloat64: My instances hold 64-bit Floats in heap objects. This is the only representation on 32-bit systems. But on 64-bit systems SmallFloat64 holds a subset of the full 64-bit double-precision range in immediate objects. > > I think that we can improve such comments but I do not have the knowledge. > > So do I get that we will have instances of Float and BoxedFloat64? > > > Le 1/2/16 21:27, Nicolas Cellier a Ã©crit : >> SmallFloat is like SmallInteger: immediate value encoded in oop, and it is only for 64 bits Spur VM. >> Boxed is the classical VM Float, two 4-bytes word allocated per Float, and is both for 32 bits VM and Float values not fitting in immediate format (3 bits have been stolen from exponent...). >> >> 2016-02-01 20:49 GMT+01:00 stepharo <stepharo(a)free.fr>: >>> Hi >>> >>> I'm updating Pharo by example and the relationship between Float and its subclasses is unclear to me. >>> Do we only get instances of the subclasses now? >>> >>> I got that Boxed is only for 64 bits. >>> But SmallFloat? >>> The class comment is not really self describing. >>> >>> Stef >

Feb. 2, 2016

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

by stepharo

What about something like that My instances hold 64-bit Floats in heap objects. This is the only representation on 32-bit systems. But on 64-bit systems SmallFloat64 holds a subset of the full 64-bit double-precision range in immediate objects. BoxedFloat64 is the classical VM Float, two 4-bytes word allocated per Float, and is both for 32 bits VM and Float values not fitting in immediate format. This is because 3 bits have been removed from the exponent due to the object internal representation needed for the Spur new garbage collector. So on a 32 bits VM Floats are represented either by BoxedFloat64 or Float.

Feb. 2, 2016

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

by stepharo

Tx nicolas I read SmallFloat64: My instances represent 64-bit Floats whose exponent fits in 8 bits as immediate objects. This representation is only available on 64-bit systems, not 32-bit systems. BoxedFloat64: My instances hold 64-bit Floats in heap objects. This is the only representation on 32-bit systems. But on 64-bit systems SmallFloat64 holds a subset of the full 64-bit double-precision range in immediate objects. I think that we can improve such comments but I do not have the knowledge. So do I get that we will have instances of Float and BoxedFloat64? Le 1/2/16 21:27, Nicolas Cellier a Ã©crit : > SmallFloat is like SmallInteger: immediate value encoded in oop, and > it is only for 64 bits Spur VM. > Boxed is the classical VM Float, two 4-bytes word allocated per Float, > and is both for 32 bits VM and Float values not fitting in immediate > format (3 bits have been stolen from exponent...). > > 2016-02-01 20:49 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Hi > > I'm updating Pharo by example and the relationship between Float > and its subclasses is unclear to me. > Do we only get instances of the subclasses now? > > I got that Boxed is only for 64 bits. > But SmallFloat? > The class comment is not really self describing. > > Stef > >

Feb. 2, 2016

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

by Nicolas Cellier

SmallFloat is like SmallInteger: immediate value encoded in oop, and it is only for 64 bits Spur VM. Boxed is the classical VM Float, two 4-bytes word allocated per Float, and is both for 32 bits VM and Float values not fitting in immediate format (3 bits have been stolen from exponent...). 2016-02-01 20:49 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi > > I'm updating Pharo by example and the relationship between Float and its > subclasses is unclear to me. > Do we only get instances of the subclasses now? > > I got that Boxed is only for 64 bits. > But SmallFloat? > The class comment is not really self describing. > > Stef > >

Feb. 1, 2016

what is the relationship between Float and its subclasses?

by stepharo

Hi I'm updating Pharo by example and the relationship between Float and its subclasses is unclear to me. Do we only get instances of the subclasses now? I got that Boxed is only for 64 bits. But SmallFloat? The class comment is not really self describing. Stef

Feb. 1, 2016

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

by Nicolai Hess

2016-02-01 16:40 GMT+01:00 stepharo <stepharo(a)free.fr>: > so do we define a bug entry? > no, not needed. > > Le 1/2/16 10:51, Esteban Lorenzano a Ã©crit : > > > On 01 Feb 2016, at 08:24, Nicolai Hess < <nicolaihess(a)gmail.com> > nicolaihess(a)gmail.com> wrote: > > > > 2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecque < > cyril.ferlicot(a)gmail.com>: > >> >> >> On 31/01/2016 15:23, stepharo wrote: >> > Hi guys >> > >> > Thanks for this fix. >> > I will start recording videos. >> > >> > Stef >> > >> > > >> >> In the last image I get errors all the time when I use unimplemented >> methods. >> I think this might be related if this was done to add syntax >> highlighting for unimplemented methods. >> > > unlikely, many 'icon'-methods are now rendered as 'unimplemeted' methods, > because > ThemeIcons uses #doesNotUnderstand indirection to create the named icons. > And that seems to work > well. > > > then this is a good reason to remove those calls (I implemented them like > that to provide compatibility, but correct way should be to use > #iconNamed:â¦) :) > > Esteban > > And the error about > > RubShoutStylerDecorator(Object)>>doesNotUnderstand: > #recomposeFrom:to:delta: > happened already to me, sometimes, before we made this change for the > (Symbol SelectorTabe). > > What exactly had you done when this error occured. editing a new > method/edit an existing method but > call a new unimplemented method/writing some code in playground, using > unimplemented methods? > > > >> RubShoutStylerDecorator(Object)>>doesNotUnderstand: >> #recomposeFrom:to:delta: >> [ super doesNotUnderstand: aMessage ] in >> RubShoutStylerDecorator(RubParagraphDecorator)>>doesNotUnderstand: >> #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] >> BlockClosure>>cull: >> Context>>evaluateSignal: >> Context>>handleSignal: >> MessageNotUnderstood(Exception)>>signal >> RubCurrentLineBarDecorator(Object)>>doesNotUnderstand: >> #recomposeFrom:to:delta: >> [ super doesNotUnderstand: aMessage ] in >> RubCurrentLineBarDecorator(RubParagraphDecorator)>>doesNotUnderstand: >> #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] >> BlockClosure>>cull: >> Context>>evaluateSignal: >> Context>>handleSignal: >> MessageNotUnderstood(Exception)>>signal >> RubExtraSelectionDecorator(Object)>>doesNotUnderstand: >> #recomposeFrom:to:delta: >> [ super doesNotUnderstand: aMessage ] in >> RubExtraSelectionDecorator(RubParagraphDecorator)>>doesNotUnderstand: >> #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] >> BlockClosure>>cull: >> Context>>evaluateSignal: >> Context>>handleSignal: >> MessageNotUnderstood(Exception)>>signal >> RubOpeningClosingDelimiterDecorator(Object)>>doesNotUnderstand: >> #recomposeFrom:to:delta: >> [ super doesNotUnderstand: aMessage ] in >> >> RubOpeningClosingDelimiterDecorator(RubParagraphDecorator)>>doesNotUnderstand: >> #recomposeFrom:to:delta: in Block: [ super doesNotUnderstand: aMessage ] >> BlockClosure>>cull: >> Context>>evaluateSignal: >> Context>>handleSignal: >> MessageNotUnderstood(Exception)>>signal >> RubTextMethodLink(Object)>>doesNotUnderstand: #tes >> RubTextMethodLink(TextLink)>>= >> Array(SequenceableCollection)>>hasEqualElements: >> Array(SequenceableCollection)>>= >> Array(SequenceableCollection)>>hasEqualElements: >> RunArray>>= >> >> -- >> Cyril > > > >

Feb. 1, 2016