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

Re: [Pharo-dev] macOS Sierra support

by Marcus Denker

Do we use this the CI? Are the downloadable artefacts being build with it? > On 4 Oct 2016, at 11:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > this one: > > pharo-mac-i386.zip <https://bintray.com/estebanlm/pharo-vm/download_file?file_path=pharo-mac-i3…> > > should be working fine. > Still that âold VMâ message, and some problems related to how the versions string are handled now, but I think is doing ok. > Also, still no signingâ¦ We will do that soon :) > > Esteban > >> On 4 Oct 2016, at 10:06, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >> >> >>> On 27 Sep 2016, at 13:46, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>> >>>> >>>> On 27 Sep 2016, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>> >>>>> On 27 Sep 2016, at 11:15, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> Can someone who really knows/understand please describe where to find the necessary Pharo VM's to run on the newly released macOS Sierra (10.12) ? >>>> >>>> Iâm in the process of producing compatible VMs. >>>> Today or tomorrow they will be ready. >>> >>> OK, looking forward to it, we will certainly test. >> >> Any progress ? >> >> << Starting today, Apple is making the new macOS Sierra operating system available as an automatic download to customers running OS X El Capitan in order to encourage them to update. >> >> Customers who have auto downloads enabled will see macOS Sierra start to download automatically, but it will not install without express user permission. >> >> >> Which means many more people will get in trouble. >> >> >

Oct. 4, 2016

Re: [Pharo-dev] macOS Sierra support

by Esteban Lorenzano

this one: pharo-mac-i386.zip <https://bintray.com/estebanlm/pharo-vm/download_file?file_path=pharo-mac-i3…> should be working fine. Still that âold VMâ message, and some problems related to how the versions string are handled now, but I think is doing ok. Also, still no signingâ¦ We will do that soon :) Esteban > On 4 Oct 2016, at 10:06, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 27 Sep 2016, at 13:46, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 27 Sep 2016, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> On 27 Sep 2016, at 11:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Hi, >>>> >>>> Can someone who really knows/understand please describe where to find the necessary Pharo VM's to run on the newly released macOS Sierra (10.12) ? >>> >>> Iâm in the process of producing compatible VMs. >>> Today or tomorrow they will be ready. >> >> OK, looking forward to it, we will certainly test. > > Any progress ? > > << Starting today, Apple is making the new macOS Sierra operating system available as an automatic download to customers running OS X El Capitan in order to encourage them to update. > > Customers who have auto downloads enabled will see macOS Sierra start to download automatically, but it will not install without express user permission. >> > > Which means many more people will get in trouble. > >

Oct. 4, 2016

Re: [Pharo-dev] macOS Sierra support

by Dimitris Chloupis

Pharo runs fine on MacOS Sierra , I did get a blank window with a download I made during El Capitan but re downloading latest vm and image works flawlessly On Tue, Oct 4, 2016 at 11:07 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 27 Sep 2016, at 13:46, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> > >> On 27 Sep 2016, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >>> On 27 Sep 2016, at 11:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>> > >>> Hi, > >>> > >>> Can someone who really knows/understand please describe where to find > the necessary Pharo VM's to run on the newly released macOS Sierra (10.12) ? > >> > >> Iâm in the process of producing compatible VMs. > >> Today or tomorrow they will be ready. > > > > OK, looking forward to it, we will certainly test. > > Any progress ? > > << Starting today, Apple is making the new macOS Sierra operating system > available as an automatic download to customers running OS X El Capitan in > order to encourage them to update. > > Customers who have auto downloads enabled will see macOS Sierra start to > download automatically, but it will not install without express user > permission. >> > > Which means many more people will get in trouble. > > >

Oct. 4, 2016

Re: [Pharo-dev] macOS Sierra support

by Sven Van Caekenberghe

> On 27 Sep 2016, at 13:46, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 27 Sep 2016, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> On 27 Sep 2016, at 11:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi, >>> >>> Can someone who really knows/understand please describe where to find the necessary Pharo VM's to run on the newly released macOS Sierra (10.12) ? >> >> Iâm in the process of producing compatible VMs. >> Today or tomorrow they will be ready. > > OK, looking forward to it, we will certainly test. Any progress ? << Starting today, Apple is making the new macOS Sierra operating system available as an automatic download to customers running OS X El Capitan in order to encourage them to update. Customers who have auto downloads enabled will see macOS Sierra start to download automatically, but it will not install without express user permission. >> Which means many more people will get in trouble.

Oct. 4, 2016

Re: [Pharo-dev] How does Pharo store instance variables?

by Dimitris Chloupis

"static" the worst name for a class variable. On Tue, 4 Oct 2016 at 09:26, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: On 04/10/16 03:37, CodeDmitry wrote: > "static" variables in Pharo outlive their Playground call! There is no such thing as a "static" method or "static" variable in Smalltalk. At least not in the Java sense. In most languages a static method is simply a function attached to a class (because there is no other place to put it). But it does not imply any meaning to this/self. It's similar for variables ... because Global Variables are frowned upon most programmers simply attach them to a class - making them "static". That's different in Smalltalk. In Smalltalk /every method is an instance method/! "Regular methods" are defined by the instance's class and executed within an instance context. "Class methods" are defined by the instances's *meta*class and also executed in an instance context - only that the instance at that point is the class itself! Because there is a 1:1 relationship between the class (defining the instance behavior) and it's meta-class (defining the class behavior) the Smalltalk Browser provides a unified view. E.g. if you create a class in the class browser you'll also create it's metaclass. The code you see when browsing "the instance side" is the method dictionary of the class. If you switch to "the class side" in the class browser you are essentially browsing the method dictionary of it's metaclass! It's a bit more complex for variables. Ignoring regular instance variables a "class variable" is defined by a class and is shared with all it's subclasses. E.g. a class hierarchy, where only one of the subclasses is used for a Singleton at a time could use a class variable "Current". A "class instance variable" on the other hand does not share it's value with subclasses. E.g. the class name and it's method dictionary could be candidates for class inctance variables - i.e. they are unique per class - not per hierarchy! IMHO this implementation of instances/classes/metaclasses is very different from the "static" stuff used today. Take a look here (especially Chapter 5 in the Blue Book) for more details: http://esug.org/data/Articles/Columns/EwingPapers/cvars&cinst_vars.pdf http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook.pdf CU, Udo

Oct. 4, 2016

[pharo-project/pharo-core]

by GitHub

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

Oct. 4, 2016

[pharo-project/pharo-core] ddb5a5: 60249

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ddb5a531c79208d72826fa86718ef75c5d215ef6 https://github.com/pharo-project/pharo-core/commit/ddb5a531c79208d72826fa86… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-04 (Tue, 04 Oct 2016) Changed paths: M Collections-Sequenceable.package/OrderedDictionary.class/instance/adding/addAll_.st M Collections-Sequenceable.package/OrderedDictionary.class/instance/printing/printElementsOn_.st A Collections-Sequenceable.package/OrderedDictionary.class/instance/removing/removeKeys_.st R Collections-Tests.package/DictionaryTest.class/instance/test - integrity/testAllDictionariesAreHealthy.st M Collections-Tests.package/OrderedDictionaryTest.class/README.md A Collections-Tests.package/OrderedDictionaryTest.class/class/testing/shouldInheritSelectors.st M Collections-Tests.package/OrderedDictionaryTest.class/definition.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/changedOrderedAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/changedOrderedAssociationsFirst_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryAssociations.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryKeys.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryValues.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryWithAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryWithOrderedAssociations.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/dictionaryWithSingleAssociation.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/identityAbsentKey.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/identityDictionaryAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/identityOrderedAssociations.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/internalDictionaryWithAssociations.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/internalDictionaryWithSingleAssociation.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/newKey.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/nonIdentityDictionaryAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/nonIdentityOrderedAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedAssociations.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedAssociationsAllButFirst_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedAssociationsFirst_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedKeys.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedKeysFirst_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedValues.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/orderedValuesFirst_.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/otherOrderedDictionaryClasses.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/singleAssociation.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/singleKey.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/accessing/singleValue.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertDictionary_doesNotEqual_.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertDictionary_equals_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertIsArray_withElements_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertIsDictionary_copiedFrom_withOrderedAssociations_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertIsDictionary_withAssociations_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertIsDictionary_withOrderedAssociations_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertKey_wasRemovedfrom_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertRemovedKey_from_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertSelector_collects_from_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertSelector_enumerates_and_from_.st R Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/assertSelector_enumerates_from_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/should_enumerate_.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/assertions/should_enumerate_and_.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAdd.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAddAll.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociationAt.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociationAtIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociationAtIfPresent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociations.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociationsDo.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAssociationsSelect.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAt.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAtIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAtIfAbsentPut.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAtIfPresent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAtIfPresentIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testAtPut.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testBindingsDo.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testCapacity.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testCollect.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testCopy.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testCopyEmpty.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testDeclareFrom.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testDictionary.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testDo.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testEquals.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testEqualsDictionary.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testEqualsOtherOrderedDictionaries.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testHash.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIdentityIndexOfKey.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIdentityIndexOfKeyIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIncludes.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIncludesAssociation.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIncludesIdentity.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIncludesKey.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIndexOfKey.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testIndexOfKeyIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIdentityValue.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIdentityValueIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIndex.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtIndexIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtValue.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyAtValueIfAbsent.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeyForIdentity.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeys.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeysAndValuesDo.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeysAndValuesRemove.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeysDo.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testKeysSortedSafely.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testNewFrom.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testNewFromPairs.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testOccurancesOf.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testRemoveAll.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testRemoveKey.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testRemoveKeyIfAbsent.st A Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testRemoveKeys.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testSelect.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testSize.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testValues.st M Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testValuesDo.st R Collections-Tests.package/OrderedIdentityDictionaryTest.class/class/testing/shouldInheritSelectors.st R Collections-Tests.package/SetTest.class/instance/some tests/testAllSetsAreHealthy.st M Collections-Unordered.package/SmallDictionary.class/instance/testing/isHealthy.st R Kernel-Tests.package/MethodDictionaryTest.class/instance/tests - integrity/testAllMethodDictionariesAreHealthy.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60248.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60249.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60248.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60249.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/BooleanSlot.class/instance/class building/layoutChanged_.st M Slot.package/PropertySlot.class/instance/class building/layoutChanged_.st M Slot.package/UnlimitedInstanceVariableSlot.class/instance/class building/layoutChanged_.st Log Message: ----------- 60249 19130 Deprecation: The method Object>>name in Slot https://pharo.fogbugz.com/f/cases/19130 19167 OrderedDictionary improvements https://pharo.fogbugz.com/f/cases/19167 http://files.pharo.org/image/60/60249.zip

Oct. 4, 2016

Re: [Pharo-dev] How does Pharo store instance variables?

by Udo Schneider

On 04/10/16 03:37, CodeDmitry wrote: > "static" variables in Pharo outlive their Playground call! There is no such thing as a "static" method or "static" variable in Smalltalk. At least not in the Java sense. In most languages a static method is simply a function attached to a class (because there is no other place to put it). But it does not imply any meaning to this/self. It's similar for variables ... because Global Variables are frowned upon most programmers simply attach them to a class - making them "static". That's different in Smalltalk. In Smalltalk /every method is an instance method/! "Regular methods" are defined by the instance's class and executed within an instance context. "Class methods" are defined by the instances's *meta*class and also executed in an instance context - only that the instance at that point is the class itself! Because there is a 1:1 relationship between the class (defining the instance behavior) and it's meta-class (defining the class behavior) the Smalltalk Browser provides a unified view. E.g. if you create a class in the class browser you'll also create it's metaclass. The code you see when browsing "the instance side" is the method dictionary of the class. If you switch to "the class side" in the class browser you are essentially browsing the method dictionary of it's metaclass! It's a bit more complex for variables. Ignoring regular instance variables a "class variable" is defined by a class and is shared with all it's subclasses. E.g. a class hierarchy, where only one of the subclasses is used for a Singleton at a time could use a class variable "Current". A "class instance variable" on the other hand does not share it's value with subclasses. E.g. the class name and it's method dictionary could be candidates for class inctance variables - i.e. they are unique per class - not per hierarchy! IMHO this implementation of instances/classes/metaclasses is very different from the "static" stuff used today. Take a look here (especially Chapter 5 in the Blue Book) for more details: http://esug.org/data/Articles/Columns/EwingPapers/cvars&cinst_vars.pdf http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook.pdf CU, Udo

Oct. 4, 2016

Re: [Pharo-dev] How does Pharo store instance variables?

by serge.stinckwich＠gmail.com

Hi guys, I think such discussions should be done in pharo-users. These discussions will be very interesting to follow by users/beginners. Pharo-dev is more about contributions/discussions aboit core development of Pharo. Thank you EnvoyÃ© de mon iPhone > Le 4 oct. 2016 Ã 05:00, Ben Coman <btc(a)openinworld.com> a Ã©crit : > >> On Tue, Oct 4, 2016 at 9:37 AM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: >> Oh! I see where I got confused now! >> >> "static" variables in Pharo outlive their Playground call! > > More than that. They outlive closing the image. The paradigm*** shift > you need to make is that while the lifetime of "static" variables of a > C/C++ program ends when program execution ends, and even though you > stop and start execution of the VM, the execution of the "Image" > *never* ends, it is only suspended. > > Try this experiment... > > In the System Browser... > Morph subclass: #MyMorph > instanceVariableNames: '' > classVariableNames: '' > package: 'AnExperiment' > > MyMorph>>step > self right > Display width ifTrue: [ self left: 0 ]. > self left: self left + 10. > > MyMorph>>stepTime > ^100 > > In Playground... > (m := MyMorph new) openInWorld. > "After it has been running a while, Save & Quit the image**, then > restart it. Notice the movement of the morph continues from where it > left off." > m delete. "...sometime later" > > **Even copy the image and changes to another machine they start it up there. > > *** and perhaps you might notice a change in your perception of "what > is possible" from exposure in your course to the "dead" language of > Smalltalk. And further, consider MyMorph is part of a control system > for a nuclear power plant or financial trading system operating 365x24 > and you want to change MyMorph from moving right to moving left. > Consider how you would do that in C++ without stopping the system for > even a second, compared to doing that in Pharo. Now Pharo may not be > production ready (i.e. $$$) to run a nuclear power plant, but the > concept of making such "live" changes to compiled code is now a > concept you can carry forward to other disciplines. > > cheers -ben > >> >> If I call >> >> Greeter greet. >> Greeter greeting: 'Hi!'. >> Greeter greet. >> >> Even if greet sets greeting to an initial value if it is nil, it will >> forever then stay 'Hi!' until I change it or reset it. >> >> So it is not unreasonable to get a response 'Hi! Hi!' in the playground even >> though 'Hi!' only gets set after greet is called, since the global state >> outlives the Transcript! >

Oct. 4, 2016

Re: [Pharo-dev] How does Pharo store instance variables?

by Ben Coman

On Tue, Oct 4, 2016 at 9:37 AM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > Oh! I see where I got confused now! > > "static" variables in Pharo outlive their Playground call! More than that. They outlive closing the image. The paradigm*** shift you need to make is that while the lifetime of "static" variables of a C/C++ program ends when program execution ends, and even though you stop and start execution of the VM, the execution of the "Image" *never* ends, it is only suspended. Try this experiment... In the System Browser... Morph subclass: #MyMorph instanceVariableNames: '' classVariableNames: '' package: 'AnExperiment' MyMorph>>step self right > Display width ifTrue: [ self left: 0 ]. self left: self left + 10. MyMorph>>stepTime ^100 In Playground... (m := MyMorph new) openInWorld. "After it has been running a while, Save & Quit the image**, then restart it. Notice the movement of the morph continues from where it left off." m delete. "...sometime later" **Even copy the image and changes to another machine they start it up there. *** and perhaps you might notice a change in your perception of "what is possible" from exposure in your course to the "dead" language of Smalltalk. And further, consider MyMorph is part of a control system for a nuclear power plant or financial trading system operating 365x24 and you want to change MyMorph from moving right to moving left. Consider how you would do that in C++ without stopping the system for even a second, compared to doing that in Pharo. Now Pharo may not be production ready (i.e. $$$) to run a nuclear power plant, but the concept of making such "live" changes to compiled code is now a concept you can carry forward to other disciplines. cheers -ben > > If I call > > Greeter greet. > Greeter greeting: 'Hi!'. > Greeter greet. > > Even if greet sets greeting to an initial value if it is nil, it will > forever then stay 'Hi!' until I change it or reset it. > > So it is not unreasonable to get a response 'Hi! Hi!' in the playground even > though 'Hi!' only gets set after greet is called, since the global state > outlives the Transcript!

Oct. 4, 2016