- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] opal optimize to do limits

by ClÃ©ment Bera

You can use whileTrue: if it's a problem for you not to evaluate the limit at each iteration of the loop. If you look at OrderedCollection for example, there are implemented differently in Pharo/VW and Squeak. Pharo and VW use to:do: whereas Squeak uses whileTrue: to iterate over the collection. Hence, if you remove elements from the OrderedCollection while iterating over it, the behavior is different. 2015-11-20 1:34 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Because were to:do: not inlined the expression passed as the to: actual > argument would be evaluated exactly once (bound to the formal argument for > to:) and so assigning to a temporary preserves the semantics in the most > direct way. If the expression has side effects then those side effects > must occur only once. > > Note that were the to: expression merely another variable then the > compiler could only substitute the original variable if it's value could > not change, e.g. in > > exampleToDoArgumentLimitIsExpression > | count sum | > count := 10. > sum := 0. > 1 to: count do: [ :each | sum := sum + each]. > ^sum > > It is ok to use count directly as the limit variable, but in this it is > not: > > exampleToDoArgumentLimitIsExpression > | count sum | > count := 10. > sum := 0. > 1 to: count do: [ :each | sum := sum + each. count := > #somethingElseEntirely]. > ^sum > > _,,,^..^,,,_ (phone) > > > On Nov 19, 2015, at 1:14 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > What is the purpose of replacing expressions, used as limits in a > > to:do: call with by a new temporary variable? > > > > For example: > > > > OCOpalExamples>>#exampleToDoArgumentLimitIsExpression > > the code is > > > > exampleToDoArgumentLimitIsExpression > > | count sum | > > count := 10. > > sum := 0. > > 1 to: count - 1 do: [ :each | sum := sum + each]. > > ^sum > > > > the decompiled bytecode : > > > > exampleToDoArgumentLimitIsExpression > > | tmp1 tmp2 tmp3 | > > tmp1 := 10. > > tmp2 := 0. > > tmp3 := tmp1 - 1. > > 1 to: tmp3 do: [ :tmp4 | tmp2 := tmp2 + tmp4 ]. > > ^ tmp2 > > > > So, the expression (count - 1) in the to:do: loop is replaced by a new > > temporay (tmp3). > > > > Ok, but why ? > >

Nov. 20, 2015

Re: [Pharo-dev] News about FastTable

by Thierry Goubier

Le 19/11/2015 23:34, Stephan Eggermont a Ã©crit : > On 19/11/15 16:27, Thierry Goubier wrote: >> I have a very clear idea of how complex that feature you are asking for >> is to implement properly in the general case and I won't consider >> implementing it if there is no strong justification for it. > > In Cocoa this is delegated behaviour. The Macintosh Finder just loses > selection in the subtree when closing its parent. Somewhere I've seen > the described behaviour, I think in an installer somewhere, could be an > Adobe product. The selection announcements of FT would allow the model to implement that. I think it would be bizarre to see it working with drag and drop: it would either make hidden items reappear when starting the drag (selected items in a closed subtree), or drag partially selected items. Now, what I'd like on drag and drop is: automatic expand after a timeout hovering over a node, and automatic scrollbar up and down when dragging over the top / the bottom of the tree :) Thierry

Nov. 20, 2015

Re: [Pharo-dev] opal optimize to do limits

by Eliot Miranda

Because were to:do: not inlined the expression passed as the to: actual argument would be evaluated exactly once (bound to the formal argument for to:) and so assigning to a temporary preserves the semantics in the most direct way. If the expression has side effects then those side effects must occur only once. Note that were the to: expression merely another variable then the compiler could only substitute the original variable if it's value could not change, e.g. in exampleToDoArgumentLimitIsExpression | count sum | count := 10. sum := 0. 1 to: count do: [ :each | sum := sum + each]. ^sum It is ok to use count directly as the limit variable, but in this it is not: exampleToDoArgumentLimitIsExpression | count sum | count := 10. sum := 0. 1 to: count do: [ :each | sum := sum + each. count := #somethingElseEntirely]. ^sum _,,,^..^,,,_ (phone) > On Nov 19, 2015, at 1:14 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > What is the purpose of replacing expressions, used as limits in a > to:do: call with by a new temporary variable? > > For example: > > OCOpalExamples>>#exampleToDoArgumentLimitIsExpression > the code is > > exampleToDoArgumentLimitIsExpression > | count sum | > count := 10. > sum := 0. > 1 to: count - 1 do: [ :each | sum := sum + each]. > ^sum > > the decompiled bytecode : > > exampleToDoArgumentLimitIsExpression > | tmp1 tmp2 tmp3 | > tmp1 := 10. > tmp2 := 0. > tmp3 := tmp1 - 1. > 1 to: tmp3 do: [ :tmp4 | tmp2 := tmp2 + tmp4 ]. > ^ tmp2 > > So, the expression (count - 1) in the to:do: loop is replaced by a new > temporay (tmp3). > > Ok, but why ?

Nov. 20, 2015

Re: [Pharo-dev] opal optimize to do limits

by Nicolai Hess

2015-11-19 22:29 GMT+01:00 stepharo <stepharo(a)free.fr>: > SSA form? > > and for method arguments? foo: count | sum | sum := 0. 1 to: count do: [ :ku | sum := sum + ku ]. ^ sum transforms to: "foo: arg1 | tmp1 tmp2 | tmp1 := 0. tmp2 := arg1. 1 to: tmp2 do: [ :tmp3 | tmp1 := tmp1 + tmp3 ]. ^ tmp1" > Le 19/11/15 22:14, Nicolai Hess a Ã©crit : > > What is the purpose of replacing expressions, used as limits in a >> to:do: call with by a new temporary variable? >> >> For example: >> >> OCOpalExamples>>#exampleToDoArgumentLimitIsExpression >> the code is >> >> exampleToDoArgumentLimitIsExpression >> | count sum | >> count := 10. >> sum := 0. >> 1 to: count - 1 do: [ :each | sum := sum + each]. >> ^sum >> >> the decompiled bytecode : >> >> exampleToDoArgumentLimitIsExpression >> | tmp1 tmp2 tmp3 | >> tmp1 := 10. >> tmp2 := 0. >> tmp3 := tmp1 - 1. >> 1 to: tmp3 do: [ :tmp4 | tmp2 := tmp2 + tmp4 ]. >> ^ tmp2 >> >> So, the expression (count - 1) in the to:do: loop is replaced by a new >> temporay (tmp3). >> >> Ok, but why ? >> > > >

Nov. 19, 2015

Re: [Pharo-dev] About being a real Pharo Jedi developer

by Mariano Martinez Peck

To unload a package you can do it from Monticello Browser..Select the package (left column), right click, "Unload Package". But not that it will not work properly in cases where you have method overrides (the original methods you override will NOT be recovered), or class collisions (imagine your package has a class name collision with a class name of another package)... Then you can have instances of classes you unload...hence the Obsolete thingy (instances are now instance of an obsolete class). Then you can also have subclasses in ANOTHER package of classes of the package you unload. What you do with the subclasses? and with the instances of such subclasses? So... order of unloading does matter across packages (in the same way that loading does). So for unloading multiple packages you should be using Meacello or similar. As you can see, it's not an easy task. On Thu, Nov 19, 2015 at 7:23 PM, milton mamani <akevalion(a)gmail.com> wrote: > +1 > By the way so how one can unload a project from the pharo image ? I never > tried that one before. > > Use the Force Dimitris > > Sorry I dont have the answer for this now, but I am interested on this > issue. > > 2015-11-19 18:05 GMT-04:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> I prefer being a technomage to a jedi, jedies are too, well naive and >> purists. >> >> By the way so how one can unload a project from the pharo image ? I never >> tried that one before. >> >> On Thu, Nov 19, 2015 at 10:59 PM stepharo <stepharo(a)free.fr> wrote: >> >>> When I was getting to be a Jedi, my Yoda master (Joseph Pelrine) told me >>> the following (yes back in 96) >>> >>> translated from Yoda language: >>> >>> you will be a real Jedi when your code will load in one click! >>> you will be a real Jedi when your code will unload in one click and >>> do not let shit behind it! >>> >>> Simple no. So when do we get real Jedi knights? >>> >>> Stef >>> >>> > -- Mariano http://marianopeck.wordpress.com

Nov. 19, 2015

Re: [Pharo-dev] News about FastTable

by Stephan Eggermont

On 19/11/15 16:27, Thierry Goubier wrote: > I have a very clear idea of how complex that feature you are asking for > is to implement properly in the general case and I won't consider > implementing it if there is no strong justification for it. In Cocoa this is delegated behaviour. The Macintosh Finder just loses selection in the subtree when closing its parent. Somewhere I've seen the described behaviour, I think in an installer somewhere, could be an Adobe product. Stephan

Nov. 19, 2015

Re: [Pharo-dev] About being a real Pharo Jedi developer

by milton mamani

+1 By the way so how one can unload a project from the pharo image ? I never tried that one before. Use the Force Dimitris Sorry I dont have the answer for this now, but I am interested on this issue. 2015-11-19 18:05 GMT-04:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > I prefer being a technomage to a jedi, jedies are too, well naive and > purists. > > By the way so how one can unload a project from the pharo image ? I never > tried that one before. > > On Thu, Nov 19, 2015 at 10:59 PM stepharo <stepharo(a)free.fr> wrote: > >> When I was getting to be a Jedi, my Yoda master (Joseph Pelrine) told me >> the following (yes back in 96) >> >> translated from Yoda language: >> >> you will be a real Jedi when your code will load in one click! >> you will be a real Jedi when your code will unload in one click and >> do not let shit behind it! >> >> Simple no. So when do we get real Jedi knights? >> >> Stef >> >>

Nov. 19, 2015

Re: [Pharo-dev] About being a real Pharo Jedi developer

by Chris Muller

> translated from Yoda language: > > you will be a real Jedi when your code will load in one click! In Yoda grammar: "When, in one click, your code will load, then, and only then, a Jedi will you be..." :)

Nov. 19, 2015

Re: [Pharo-dev] About being a real Pharo Jedi developer

by Dimitris Chloupis

I prefer being a technomage to a jedi, jedies are too, well naive and purists. By the way so how one can unload a project from the pharo image ? I never tried that one before. On Thu, Nov 19, 2015 at 10:59 PM stepharo <stepharo(a)free.fr> wrote: > When I was getting to be a Jedi, my Yoda master (Joseph Pelrine) told me > the following (yes back in 96) > > translated from Yoda language: > > you will be a real Jedi when your code will load in one click! > you will be a real Jedi when your code will unload in one click and > do not let shit behind it! > > Simple no. So when do we get real Jedi knights? > > Stef > >

Nov. 19, 2015

Re: [Pharo-dev] thanks for 17010

by Dimitris Chloupis

and I thank you for fixing the problem with the shortcuts in pharo 5 :) Ah the never ending game of seeking funds, sounds fun :D On Thu, Nov 19, 2015 at 11:12 PM stepharo <stepharo(a)free.fr> wrote: > 50451 > 17010 MultistateButtonMorph to use announcement instead of > #triggerEvent: > https://pharo.fogbugz.com/f/cases/17010 > > I'm too busy running around like an idiot to find money for the future > (my real job in fact - I'm not a great scientist - I'm a excel budgeter) > but this is cool to see this happening. > > Thanks Henrik > > > >

Nov. 19, 2015