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

Re: [Pharo-dev] Pharo bootstrap

by Craig Latta

Hi all-- Phil writes: > The point is not to clean but to start with an empty object engine and > fill it in with the minimum required core. Currently, the image is > the result of an evolutionary process and rebuilding it from zero was > not possible. Another approach is to modify the virtual machine so that it marks methods as they are run, and modify the garbage collector to reclaim methods that haven't been run. Then you can create systems that consist of only what is necessary to run unit tests, effectively imprinting the unit tests. You can interact with the target system from completely independent one over a remote messaging network connection, so your unit tests need not include graphics support, etc.[1] This seems much simpler to me than making a virtual machine that can run multiple object memories, and distributed object memories have several other important uses too. > This makes it possible to audit the whole build process, create > different base image for various purposes (very small, headless with > no UI objects at all, using the object engine in a completely > different way that is used today). > > That makes the image the result of a fully reproducible process, from > a file of zero bytes, to a file with a working image. You can do all of these things with imprinted unit tests as well. > Also, this allows to experiment with new low level mechanisms. This is > currently not possible since it makes us like performing surgery on > our own brain. With remote messaging, which has been around for many years, you can perform this surgery from afar. > Also, the Oz-inspired system will help in exploring other image > memories (small or large) and manipulate them as entities. At this > point, this is also not common pratice. This has been common practice since the introduction of the virtual machine simulator in 1996. The remote facilities I mentioned all work under simulation, too. There's a lot of prior art here. -C [1] http://netjam.org/context -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Jan. 20, 2016

Re: [Pharo-dev] Rubric: spotter with preview leaks some memory

by Nicolai Hess

2016-01-20 14:47 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > Tried it in the last latest image and if I execute before #garbageCollect > I just get 4 instances. > > Smalltalk garbageCollect. > RubTextLine allInstances size "4" > > Now indeed if I browse the same class in nautilus I get a much smaller > number of RubTextLine instances > I opened a bugreport 17437 <https://pharo.fogbugz.com/f/cases/17437/Rubric-spotter-with-preview-leaks-s…> Rubric: spotter with preview leaks some memory > > On Wed, Jan 20, 2016 at 2:32 PM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> Open fresh image 50536 >> Open Spotter, >> enable preview (cmd+p) >> search for EllipseMorph >> dive in instance-methods >> scroll through the list one item after another. >> >> open playground >> evaluate >> RubTextLine allInstances size. "553896" >> >> >> case 17421 is related to this, but does not fully solves this. >> please review and comment on that fix, >> so we can integrate this soon. >> >> The problem sometimes remains even with this fix. The memory >> (instance count of RubTextLine) just grows in the background >> > >

Jan. 20, 2016

Re: [Pharo-dev] [ANN] Pharo bootstrap

by phil＠highoctane.be

On Wed, Jan 20, 2016 at 4:19 PM, Peter H. Meadows via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: "Peter H. Meadows" <peter.h.meadows(a)googlemail.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Wed, 20 Jan 2016 15:17:59 +0000 > Subject: Re: [Pharo-dev] [ANN] Pharo bootstrap > Cool. Any chance someone can explain for beginners to understand > what's going on here? > Why is cleaning the image not as simple as running it and deleting any > object that wasn't used? > The point is not to clean but to start with an empty object engine and fill it in with the minimum required core. Currently, the image is the result of an evolutionary process and rebuilding it from zero was not possible. This maes it possible to audit the whole build process, create different base image for various purposes (very small, headless with no UI objects at all, using the object engine in a completely different way that is used today). That makes the image the result of a fully reproducible process, from a file of zero bytes, to a file with a working image. That would make us master the whole chain. Today, there is still black magic in the image, due to the history. That's an exciting development. For example, in C, one compiles all files, and links, giving the exe. All that from a file of zero size. We will be able to do the same kind of thing at the image level. Also, this allows to experiment with new low level mechanisms. This is currently not possible since it makes us like performing surgery on our own brain. Also, the Oz-inspired system will help in exploring other image memories (small or large) and manipulate them as entities. At this point, this is also not common pratice. HTH Phil, wishing to master the mitosis competency... > > (Thanks in advance) > > On 20 January 2016 at 12:52, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Well, there is no formal specificationâ¦ But I could summarize the > features > > as follows (and as Christophe points mostly out) > > > > OzVM supports having two images in logically separated spaces. This > > separation is achieved by using the free bit in the object header. Thus > we > > support only two spaces by now. > > > > - The main addition is actually a new primitive: > > #resumeFromSpecialObjectsArray that receives an special objects array as > > argument and: > > - resumes the execution from the active process of such array > > - on context switch, if the VM is running from a second special > objects > > array, it will return to the first one instead. > > > > - fixes to primitives/bytecodes that assume a single special objects > array. > > e.g., > > - #someObject and #nextObject should only iterate objects from the > > correct âspaceâ > > - #isNil comparisons should take the correct nil > > - the GC should set the correct nil object on Weak containers > > > > The extensions I made are about 20 overrides to StackPrimitive and > > NewObjectMemory methods. > > > > The rest is implemented completely on image side. We use mirror > primitives > > to manipulate objects from other space (as each image/space has itâs own > > selector table). > > > > I have in my long TODO list see if the "clever hackâ I did can be > supported > > in a nice manner on top of Spurâs segmented memory. However, I should > stop > > commencing new projects and start finishing them :P. > > > > On 20 ene 2016, at 9:03 a.m., Christophe Demarey > > <Christophe.Demarey(a)inria.fr> wrote: > > > > Hi Eliot, > > > > Le 19 janv. 2016 Ã 19:29, Eliot Miranda a Ã©crit : > > > > Hi All, > > > > great news! Where can I read a specification of the Oz VM > facilities? > > > > > > I do not know all the details of the Oz VM but basically, it is a > standard > > stack interpreter vm specialized to be able to run 2 images at the same > time > > on top of it. > > Guillermo made it possible by using one available bit in the object > header > > of objects to mark the ownership of an object (e.g. is my object from > image1 > > or image2?). Then, he mainly had to specialize VM primitives dealing with > > objects retrieval from memory. By example, he had to modify the garbage > > collector to set the right nil instance (yes, we have 2 images so 2 nil > > instances. we need to take the one of the active image) when an object is > > garbage collected; the primitive someObject has to return an object from > the > > active image, etc. > > There is also a way to switch execution from an image to the other just > by > > switching the special objects array reference. > > > > You can find some information in: > > https://guillep.github.io/files/publications/Poli15Thesis.pdf. > > The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace and in > > https://github.com/guillep/OzVM > > The current implementation uses Cog 6.6.1and OzVM-GuillermoPolito.22. > > I do not know if Guille has a more formal specification of the Oz VM. > > > > If you have advices on what is the best way to handle two distinct object > > (memory) spaces in Spur, they will be welcomed :) > > > > Cheers, > > Christophe > > > > > > _,,,^..^,,,_ (phone) > > > > On Jan 19, 2016, at 6:29 AM, Christophe Demarey > > <christophe.demarey(a)inria.fr> wrote: > > > > Hi all, > > > > In case you do not know, we work on bootstrapping Pharo, i.e. create a > Pharo > > image from sources, not based on a previous image (well, we use a pharo > > image to produce it but no code / state from it). > > > > This process will allow to define a minimal Pharo kernel (currently 52 > > packages but we could have it far smaller) and to modularize the whole > image > > (currently packages have too much dependencies on packages already loaded > > into the image). > > The bootstrap process also allows to write down the recipe to initialize > a > > new image from scratch (some code is missing in the image or is wrong). > In > > addition, I think we will clean a lot of historical objects that are not > > used anymore. > > > > With the amazing work done by Guillermo Polito during his Phd (around > > Espell, Oz): > https://guillep.github.io/files/publications/Poli15Thesis.pdf, > > we succeeded to get a first prototype of a bootstraped Pharo 5 image > (from > > 5.392). > > This prototype is able to run an eval command line handler and to log > output > > / errors. Not all classes are yet initialized and you cannot yet save / > > restart this image but it is a big step forward. > > It is a 4 mb image (could be half the size without unicode data). You can > > download it at: > > > http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-… > . > > > > Next steps are to have a bootstrapped image fully working, then to load > > packages on top of it (like network, sunit) to produce a minimal image. > > Then, we need to implement an Oz VM on top of Spur. > > After that, we need to work on a reliable way to build the bootstrap (not > > too sensitive to changes in the image). > > > > Christophe. > > > > ------- > > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo > > bootstrap.image --no-default-preferences eval "1 + 1" > > 2 > > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo > > bootstrap.image --no-default-preferences eval "'a' , 'b'" > > 'ab' > > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo > > bootstrap.image --no-default-preferences eval "1 / 0" > > ZeroDivide > > SmallInteger>>/ > > UndefinedObject>>DoIt > > OpalCompiler>>evaluate > > OpalCompiler(AbstractCompiler)>>evaluate: > > SmalltalkImage>>evaluate: > > > > EvaluateCommandLineHandler>>no (source is Undeclared) > > no source in EvaluateCommandLineHandler>>evaluate: in Block: no source > > BlockClosure>>on:do: > > EvaluateCommandLineHandler>>evaluate: > > EvaluateCommandLineHandler>>evaluateArguments > > EvaluateCommandLineHandler>>activate > > EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: > > > > BasicCommandLineHandler>>no (source is Undeclared) > > no source in > > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in > > Block: no source > > BlockClosure>>on:do: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > > > > BasicCommandLineHandler>>no (source is Undeclared) > > no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate > in > > Block: no source > > BlockClosure>>on:do: > > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > > PharoCommandLineHandler>>activate > > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > > > > PharoCommandLineHandler class>>no (source is Undeclared) > > no source in PharoCommandLineHandler class>>activateWith: in Block: no > > source > > NonInteractiveUIManager(UIManager)>>defer: > > PharoCommandLineHandler class>>activateWith: > > no source in BasicCommandLineHandler>>activateSubCommand: in Block: no > > source > > BlockClosure>>on:do: > > BasicCommandLineHandler>>activateSubCommand: > > BasicCommandLineHandler>>handleSubcommand > > BasicCommandLineHandler>>handleArgument: > > no source in BasicCommandLineHandler>>activate in Block: no source > > > > SmallInteger>>no (source is Undeclared) > > > > UndefinedObject>>no (source is Undeclared) > > > > AbstractCompiler>>no (source is Undeclared) > > > > SmalltalkImage>>no (source is Undeclared) > > > > BlockClosure>>no (source is Undeclared) > > > > EvaluateCommandLineHandler>>no (source is Undeclared) > > > > EvaluateCommandLineHandler>>no (source is Undeclared) > > > > CommandLineHandler class>>no (source is Undeclared) > > > > BasicCommandLineHandler>>no (source is Undeclared) > > > > BasicCommandLineHandler>>no (source is Undeclared) > > > > PharoCommandLineHandler>>no (source is Undeclared) > > > > UIManager>>no (source is Undeclared) > > > > UndefinedObject>>no (source is Undeclared) > > > > CommandLineUIManager>>no (source is Undeclared) > > > > SmalltalkImage>>no (source is Undeclared) > > > > DelayMicrosecondScheduler>>no (source is Undeclared) > > > > BlockClosure>>no (source is Undeclared) > > > > SmalltalkImage>>no (source is Undeclared) > > > > WeakArray class>>no (source is Undeclared) > > > > > > ps: source cannot be displayed because there is no formatter available in > > the bootstrap > > > > > > > > >

Jan. 20, 2016

Re: [Pharo-dev] [ANN][Invite] Pharo Sprint 29 Jan

by Marcus Denker

> On 20 Jan 2016, at 16:37, marcus.denker(a)inria.fr wrote: > > > We will organize a Pharo sprint / Moose dojo Friday, 11th September, starting at This is Friday, 29 Jan (next week). > 10:00am. (Local Time Lille). > > It will be at the Inria Lille, Building B, third floor (RMoD offices) and > at the University of Chile, Santiago de Chile. > > Remotely, you can join us on Slack or the IRC channel #pharo on > irc.freenode.net server. During the sprint, we will try to synchronize > local and remote Pharo sprinters. > > As the building is not open to the public, please contact us before if > you plan to come.

Jan. 20, 2016

[ANN][Invite] Pharo Sprint 29 Jan

by marcus.denker＠inria.fr

We will organize a Pharo sprint / Moose dojo Friday, 11th September, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices) and at the University of Chile, Santiago de Chile. Remotely, you can join us on Slack or the IRC channel #pharo on irc.freenode.net server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come.

Jan. 20, 2016

Re: [Pharo-dev] [ANN] Pharo bootstrap

by Peter H. Meadows

Cool. Any chance someone can explain for beginners to understand what's going on here? Why is cleaning the image not as simple as running it and deleting any object that wasn't used? (Thanks in advance) On 20 January 2016 at 12:52, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Well, there is no formal specificationâ¦ But I could summarize the features > as follows (and as Christophe points mostly out) > > OzVM supports having two images in logically separated spaces. This > separation is achieved by using the free bit in the object header. Thus we > support only two spaces by now. > > - The main addition is actually a new primitive: > #resumeFromSpecialObjectsArray that receives an special objects array as > argument and: > - resumes the execution from the active process of such array > - on context switch, if the VM is running from a second special objects > array, it will return to the first one instead. > > - fixes to primitives/bytecodes that assume a single special objects array. > e.g., > - #someObject and #nextObject should only iterate objects from the > correct âspaceâ > - #isNil comparisons should take the correct nil > - the GC should set the correct nil object on Weak containers > > The extensions I made are about 20 overrides to StackPrimitive and > NewObjectMemory methods. > > The rest is implemented completely on image side. We use mirror primitives > to manipulate objects from other space (as each image/space has itâs own > selector table). > > I have in my long TODO list see if the "clever hackâ I did can be supported > in a nice manner on top of Spurâs segmented memory. However, I should stop > commencing new projects and start finishing them :P. > > On 20 ene 2016, at 9:03 a.m., Christophe Demarey > <Christophe.Demarey(a)inria.fr> wrote: > > Hi Eliot, > > Le 19 janv. 2016 Ã 19:29, Eliot Miranda a Ã©crit : > > Hi All, > > great news! Where can I read a specification of the Oz VM facilities? > > > I do not know all the details of the Oz VM but basically, it is a standard > stack interpreter vm specialized to be able to run 2 images at the same time > on top of it. > Guillermo made it possible by using one available bit in the object header > of objects to mark the ownership of an object (e.g. is my object from image1 > or image2?). Then, he mainly had to specialize VM primitives dealing with > objects retrieval from memory. By example, he had to modify the garbage > collector to set the right nil instance (yes, we have 2 images so 2 nil > instances. we need to take the one of the active image) when an object is > garbage collected; the primitive someObject has to return an object from the > active image, etc. > There is also a way to switch execution from an image to the other just by > switching the special objects array reference. > > You can find some information in: > https://guillep.github.io/files/publications/Poli15Thesis.pdf. > The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace and in > https://github.com/guillep/OzVM > The current implementation uses Cog 6.6.1and OzVM-GuillermoPolito.22. > I do not know if Guille has a more formal specification of the Oz VM. > > If you have advices on what is the best way to handle two distinct object > (memory) spaces in Spur, they will be welcomed :) > > Cheers, > Christophe > > > _,,,^..^,,,_ (phone) > > On Jan 19, 2016, at 6:29 AM, Christophe Demarey > <christophe.demarey(a)inria.fr> wrote: > > Hi all, > > In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo > image from sources, not based on a previous image (well, we use a pharo > image to produce it but no code / state from it). > > This process will allow to define a minimal Pharo kernel (currently 52 > packages but we could have it far smaller) and to modularize the whole image > (currently packages have too much dependencies on packages already loaded > into the image). > The bootstrap process also allows to write down the recipe to initialize a > new image from scratch (some code is missing in the image or is wrong). In > addition, I think we will clean a lot of historical objects that are not > used anymore. > > With the amazing work done by Guillermo Polito during his Phd (around > Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, > we succeeded to get a first prototype of a bootstraped Pharo 5 image (from > 5.392). > This prototype is able to run an eval command line handler and to log output > / errors. Not all classes are yet initialized and you cannot yet save / > restart this image but it is a big step forward. > It is a 4 mb image (could be half the size without unicode data). You can > download it at: > http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-…. > > Next steps are to have a bootstrapped image fully working, then to load > packages on top of it (like network, sunit) to produce a minimal image. > Then, we need to implement an Oz VM on top of Spur. > After that, we need to work on a reliable way to build the bootstrap (not > too sensitive to changes in the image). > > Christophe. > > ------- > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "1 + 1" > 2 > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "'a' , 'b'" > 'ab' > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "1 / 0" > ZeroDivide > SmallInteger>>/ > UndefinedObject>>DoIt > OpalCompiler>>evaluate > OpalCompiler(AbstractCompiler)>>evaluate: > SmalltalkImage>>evaluate: > > EvaluateCommandLineHandler>>no (source is Undeclared) > no source in EvaluateCommandLineHandler>>evaluate: in Block: no source > BlockClosure>>on:do: > EvaluateCommandLineHandler>>evaluate: > EvaluateCommandLineHandler>>evaluateArguments > EvaluateCommandLineHandler>>activate > EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in > Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in > Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > > PharoCommandLineHandler class>>no (source is Undeclared) > no source in PharoCommandLineHandler class>>activateWith: in Block: no > source > NonInteractiveUIManager(UIManager)>>defer: > PharoCommandLineHandler class>>activateWith: > no source in BasicCommandLineHandler>>activateSubCommand: in Block: no > source > BlockClosure>>on:do: > BasicCommandLineHandler>>activateSubCommand: > BasicCommandLineHandler>>handleSubcommand > BasicCommandLineHandler>>handleArgument: > no source in BasicCommandLineHandler>>activate in Block: no source > > SmallInteger>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > AbstractCompiler>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > CommandLineHandler class>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > PharoCommandLineHandler>>no (source is Undeclared) > > UIManager>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > CommandLineUIManager>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > DelayMicrosecondScheduler>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > WeakArray class>>no (source is Undeclared) > > > ps: source cannot be displayed because there is no formatter available in > the bootstrap > > >

Jan. 20, 2016

Use cases for methods with optional parameters

by Damien Cassou

Hi, I would like to study the impact of adding optional parameters to keyword methods in Pharo. The goal of optional parameters is to facilitate the implementation of methods where some parameters are optional. For example, Seaside has: WAComponent>>request: aRequestString label: aLabelString default: aDefaultString onAnswer: aBlock ... This method of 4 arguments has only 1 required argument (aRequestString) and 3 optional ones. In the current implementation, this results in 7 additional methods that only delegate directly or indirectly to the one above: - request: - request:default: - request:default:onAnswer: - request:label: - request:label:default: - request:label:onAnswer: - request:onAnswer: Before starting to implement anything, I need to know if it makes sense. If you want to help me, please send me all the use cases you have by giving me: - the library name (and URL if not in Catalog), or "pharo" if it's in Pharo - the class where this happens - the range of selectors that make sense For the example above, this would be: - Seaside - WAComponent - request:* Thank you very much -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 20, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 20, 2016

[pharo-project/pharo-core] f76739: 50537

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: f76739bfe2d9b1fd9be13cc23587da37c1a5088c https://github.com/pharo-project/pharo-core/commit/f76739bfe2d9b1fd9be13cc2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-20 (Wed, 20 Jan 2016) Changed paths: M ReleaseTests.package/ReleaseTest.class/instance/testing/testMethodsWithUnboundGlobals.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50536.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50537.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50536.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50537.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/SlotErrorsTest.class/instance/tests/testDangerousClassesConditions.st M Slot-Tests.package/SlotIntegrationTest.class/instance/tests/testSmallIntegerLayout.st M Slot.package/DangerousClassNotifier.class/class/accessing/shouldNotBeRedefined_.st M System-Support.package/SmalltalkImage.class/instance/special objects/newSpecialObjectsArray.st M System-Support.package/SystemNavigation.class/instance/query/methodsWithUnboundGlobals.st Log Message: ----------- 50537 17267 fix senders of #compactClassesArray https://pharo.fogbugz.com/f/cases/17267 17077 ReleaseTest testMethodsWithUnboundGlobals fails for some slotexamples https://pharo.fogbugz.com/f/cases/17077 http://files.pharo.org/image/50/50537.zip

Jan. 20, 2016

Re: [Pharo-dev] [ANN] OSSubprocess v0.2.0 release

by Hilaire

https://github.com/marianopeck/OSSubprocess/ -- Dr. Geo http://drgeo.eu

Jan. 20, 2016