- Pharo-dev - lists.pharo.org

[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

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

by Andrei Chis

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 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] OSSubprocess v0.2.0 release

by Hilaire

Thanks, The link miss instructions about what it is and how to load it (load script and Pharo version) Thanks Hilaire -- Dr. Geo http://drgeo.eu

Jan. 20, 2016

Rubric: spotter with preview leaks some memory

by Nicolai Hess

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] another spotter question

by Aliaksei Syrel

On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman <btc(a)openinworld.com> wrote: > +1. Its annoying that it takes two clicks to dive into categories like > "Implementors" (one to click an item under the category to make the arrow > appear, and then another to click on it) when it would only take one if > that arrow for each category was always visible. Doru is right, always visible arrows would pollute UI. A compromise solution would be to show them on mouse hover - one click + not overcrowded interface. Cheers, Alex

Jan. 20, 2016

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

by Guillermo Polito

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 <https://guillep.github.io/files/publications/Poli15Thesis.pdf>. > The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace <http://smalltalkhub.com/#!/~Guille/ObjectSpace> and in https://github.com/guillep/OzVM <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 <mailto:christophe.demarey@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 <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-… <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] Pharo bootstrap

by Guillermo Polito

> On 20 ene 2016, at 9:08 a.m., Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi Pavel, > > Le 19 janv. 2016 Ã 19:53, Pavel Krivanek a Ã©crit : > >> Hi, >> >> amazing! Do you have any idea how to speed up it? The bootstrap process is now running on my machine about one and half hour and it is still far from finish. > > The process is indeed far too long (takes around 10 hours) on the CI server. > Reasons are: > - we use a stack interpreter VM > - we modified it and is a bit slower than a classical stack VM Not quite so. My measurements did not show thatâ¦ But I can understand the feeling as the StackVM is in general half as fast as the CogVM, which is the VM we are used to use since years. > - we use AST interpretation to build the bootstrap and it is very slow. Guille already did some speed improvements by avoiding to interpret loops by example. > > I did not yet spend time on this point because I first wanted to have something working. > Definitely, this problem will be tackled when we will put in production the bootstrap. We should really measure because I see three main aspects: 1) class creation (executes the class builder using AST interpretation) 2) method compilation 3) method installation (using AST interpretation to respect trait copying) My feeling (from what I observe only) is that most of the time is consumed in 2) and 3), and that specially it is in 3). And I particularly want to see how the growing of collections perform. > > Cheers, > Christophe > > >> Cheers, >> -- Pavel >> >> 2016-01-19 15:29 GMT+01:00 Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr>>: >> 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 <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-… <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] another spotter question

by Ben Coman

On Wed, 20 Jan 2016 at 3:37 AM stepharo <stepharo(a)free.fr> wrote: > > Hmm. Thanks for describing this way of working. > > Here is the thing. We observed users working with this, and they all used predominantly the keyboard. So, we favored keyboard use. This is not an argument for anything, and it does not mean that that is the best design, I am just telling you how we designed it. Things can change, and this is why it is important to understand how people tend to use the UI. > > So, every (and only) selection has actions. In your example, the #Menu category has a right arrow next to it. If you click on that you âDive in categoryâ. That means that if you want to dive in #Implementors, you navigate there, and then you get the option of diving in. > > We consciously chose to not show all actions all the time because that would have led to an overcrowded UI with too many things to choose from. Right now, you have 5 main things to click on and that is it. > > Now, hearing your scenario, it seems to make sense to make the category clickable as well and make it dive in that category. We will look at it (or maybe someone else does it beforehand :)). Thanks. > > Does this make more sense now? > > > Yes! I do not get why keyboard is orthogonal to direct access. > > To me what I hate in UI is UI that are showing information but do not let > you access it. > > How can I see that I can do something on the list? > The arrows only arrive when I click on ........ > So I was trying to click on the label and it did not work. Of course I > must click on the first element > of the list so that the arrow show up on the element and the label!!!!! > > +1. Its annoying that it takes two clicks to dive into categories like "Implementors" (one to click an item under the category to make the arrow appear, and then another to click on it) when it would only take one if that arrow for each category was always visible. cheers -ben > What??? > > Seriously doru. You should have asked UI blind like me to test > Spotter. > I would have recorded a session and you can see that there are > glitches that you do not even see. > I'm just continuously bumping on them. > This is why I could understand Spotter and use it only to find a > class. > > > > > > > > > This is why I like the grabbing possibility of file on mac via the icons > and the navigation from there > because I see the file it is in front of my nose and I do not to jump into > a file system (like a mail download folder > I have no clue where it is) to grab it. > So to me Spotter should offer the same. Show information and let me grab > it. Especially when this is on the suggstion > list. > > I do not understand how you solve the problem I got with shortcut btw. > > You see the point is the following. Diving can be frustrating. > If on click on the labl you get the list then it can work really well. > > Doru > > > Stef > > > > <icfedjib..png> > > --www.tudorgirba.comwww.feenk.com > > "When people care, great things can happen." > > > > > > > > >

Jan. 20, 2016

Re: [Pharo-dev] Spotter suggestions

by David Allouche

> On 20 Jan 2016, at 11:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Jan 20, 2016, at 10:48 AM, David Allouche <david(a)allouche.net> wrote: >> >> >>> On 20 Jan 2016, at 10:39, David Allouche <david(a)allouche.net> wrote: >>> >>> And some suggestion for all lists: >> >> Another one: Esc should close Spotter. > > It does. Right. I'm puzzled. I did double check before. That's how I found out about Cmd-W. Sorry for the noise.

Jan. 20, 2016