September 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12155
by StÃ©phane Ducasse Sept. 30, 2010

Sept. 30, 2010

12155 ----- - Issue 2991: PharoKernel Part 15. Part 4 - Issue 2992: PharoKernel Part 16. Thanks Pavel and Nicolas :) Stef

1 0

Re: [Pharo-project] About open lively community vs a closed, withdrawn group of programmers
by StÃ©phane Ducasse Sept. 30, 2010

Sept. 30, 2010

true ! >>>> No, but we are working together towards improving our system. > This is what you can't have in .net and/or java where community don't > have a chance to participate in development > process, but have to wait till vendor release new version, and then > start using it. >

1 0

Re: [Pharo-project] some fixes of Undeclared
by StÃ©phane Ducasse Sept. 30, 2010

Sept. 30, 2010

thanks! Stef On Sep 30, 2010, at 9:16 AM, Pavel Krivanek wrote: > Hi, > > I added issues 3016-3018 that fixes some Undeclared in latest Pharo 1.2. That makes Undeclared empty. > > Cheers > -- Pavel > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Period at end of message pattern ?
by StÃ©phane Ducasse Sept. 30, 2010

Sept. 30, 2010

We should clean all these places. Now the problem is that if the compiler is sloppy then we may have to redo that several times. So we should probably do that with opal (even if I do not like to postpone until it is there). Stef On Sep 30, 2010, at 8:25 AM, Lukas Renggli wrote: > The Pharo compiler (even more for the Squeak one) accepts all kind of > strange syntactic constructs. I remember having fixed the refactoring > engine parser dozens of times in the past years to accommodate such > abnormalities. And of course, there more code than you actually think > that uses these constructs (mostly accidental). > > Btw, there is a Code Critics rule in Grease that finds the > repeated/mis-placed dots in Smalltalk. In most other Smalltalk such > code doesn't load. > > Lukas > > > On 30 September 2010 05:46, Igor Stasenko <siguctua(a)gmail.com> wrote: >> Hmm , whats wrong with period? >> Its an empty nil-statement >> >> try evaluate: >> ....................... >> >> Of course, if such patter is then followed by temps declaration: >> >> foo. >> | a b c | >> >> then this could lead to error. >> >> But message pattern with just period? >> I don't feel its wrong. >> >> On 30 September 2010 06:00, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >>> So that's a method that is empty except for ending in a period? That probably should be an error. If the point is to have the last line of a "real" method never end in a period, then I would have a problem. >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of James Ladd [james_ladd(a)hotmail.com] >>> Sent: Wednesday, September 29, 2010 6:28 PM >>> To: pharo-project(a)lists.gforge.inria.fr >>> Subject: [Pharo-project] Period at end of message pattern ? >>> >>> Hi All, >>> >>> While filing in some sources form a friend into Redline Smalltalk the compiler generated an >>> error on the following message pattern (method signature): >>> >>> initializeBetween: aPitcher and: aBatter events: aCollectionOfEvents. >>> >>> The error was the trailing period "." >>> >>> This is acceptable in Pharo but not in the Blue Book definition. >>> >>> I think it should be an error in Pharo as well. What do you think? >>> >>> Rgs, James. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] some fixes of Undeclared
by Pavel Krivanek Sept. 30, 2010

Sept. 30, 2010

Hi, I added issues 3016-3018 that fixes some Undeclared in latest Pharo 1.2. That makes Undeclared empty. Cheers -- Pavel

1 0

[Pharo-project] Period at end of message pattern ?
by James Ladd Sept. 30, 2010

Sept. 30, 2010

Hi All, While filing in some sources form a friend into Redline Smalltalk the compiler generated an error on the following message pattern (method signature): initializeBetween: aPitcher and: aBatter events: aCollectionOfEvents. The error was the trailing period "." This is acceptable in Pharo but not in the Blue Book definition. I think it should be an error in Pharo as well. What do you think? Rgs, James.

4 3

[Pharo-project] Metacello loading default (was: Updating the Alien Squeaksource page)
by Damien Pollet Sept. 29, 2010

Sept. 29, 2010

2010/9/29 Fernando olivero <fernando.olivero(a)usi.ch>: > Then evaluate the following to get the default installation > (Smalltalk globals classNamed: 'ConfigurationOfAlien') > perform:#loadLatestVersion. I saw that many recent Metacello configurations now define ConfigurationOfWhatever loadDefault. It would be nice to switch to that idiom, and maybe make a campaign of updating existing configurations, while there are still not so many of themâ¦ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 2

Sept. 29, 2010

no idea but I want to know that too so keep us posted. On Sep 29, 2010, at 9:59 AM, Stefan Marr wrote: > Hi: > > The naive approach of subclassing Process and writing my own fork/spawn does not seem to work for some reason. > > I tried: > > Erlang>>spawn: aBlock > "Answer an ErlProcess running the code given in the parameter. > The process is scheduled." > | proc | > proc := ErlProcess > forContext: > [aBlock value. > Processor terminateActive] asContext > priority: Processor activePriority. > proc resume. > ^ proc > > This is basically what happens in BlockClosure newProcess. > > However, since I do not want to modify BlockClosure, it is not operating on self anymore ('self value' became 'aBlock value', which seems to pose a problem. For some reason, the created process crashes on accessing aBlock, were I would expect it to be available since the block is a closure, right? > Looks to me like asContext is doing something I would have to replicate, too. > > Has someone done something similar before? > > Thanks > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

4 7

Sept. 29, 2010

Stefan the first link I sent was wrong (obviously) did you check the second? Stef On Sep 29, 2010, at 9:55 PM, Stefan Marr wrote: > Stef, I had a look at the description of these fixes, but it does not look like there is something related in it. > > Eliot, the requested output is below. > But as far as I can see, it is identical. Have verified it also in the Squeak 4.1 image, all three produce the same bytecode. > > Perhaps it not the compiler directly but some closure related code? > > Thanks > Stefan > > > > Pharo 1.1: (Erlang class>>#spawn:) abstractSymbolic > > '<primitive: 19> > pushLit: Process > pushTemp: 0 > closureNumCopied: 1 numArgs: 0 bytes 51 to 59 > pushConstant: 1 > send: #halt (0 args) > pop > pushTemp: 0 > send: #value (0 args) > pop > pushLit: Processor > send: #terminateActive (0 args) > blockReturn > send: #asContext (0 args) > pushLit: Processor > send: #activePriority (0 args) > send: #forContext:priority: (2 args) > popIntoTemp: 1 > pushTemp: 1 > send: #resume (0 args) > pop > pushTemp: 1 > returnTop > ' > > Pharo 1.1: (Erlang class>>#spawn:) symbolic. > '<primitive: 19> > 45 <41> pushLit: Process > 46 <10> pushTemp: 0 > 47 <8F 10 00 09> closureNumCopied: 1 numArgs: 0 bytes 51 to 59 > 51 <76> pushConstant: 1 > 52 <D3> send: halt > 53 <87> pop > 54 <10> pushTemp: 0 > 55 <C9> send: value > 56 <87> pop > 57 <45> pushLit: Processor > 58 <D4> send: terminateActive > 59 <7D> blockReturn > 60 <D2> send: asContext > 61 <45> pushLit: Processor > 62 <D6> send: activePriority > 63 <F0> send: forContext:priority: > 64 <69> popIntoTemp: 1 > 65 <11> pushTemp: 1 > 66 <D7> send: resume > 67 <87> pop > 68 <11> pushTemp: 1 > 69 <7C> returnTop > ' > > Squeak 4.2: (Erlang class>>#spawn:) abstractSymbolic. > '<primitive: 19> > pushLit: Process > pushTemp: 0 > closureNumCopied: 1 numArgs: 0 bytes 51 to 59 > pushConstant: 1 > send: #halt (0 args) > pop > pushTemp: 0 > send: #value (0 args) > pop > pushLit: Processor > send: #terminateActive (0 args) > blockReturn > send: #asContext (0 args) > pushLit: Processor > send: #activePriority (0 args) > send: #forContext:priority: (2 args) > popIntoTemp: 1 > pushTemp: 1 > send: #resume (0 args) > pop > pushTemp: 1 > returnTop > ' > > Squeak 4.2: (Erlang class>>#spawn:) symbolic. > > '<primitive: 19> > 45 <41> pushLit: Process > 46 <10> pushTemp: 0 > 47 <8F 10 00 09> closureNumCopied: 1 numArgs: 0 bytes 51 to 59 > 51 <76> pushConstant: 1 > 52 <D3> send: halt > 53 <87> pop > 54 <10> pushTemp: 0 > 55 <C9> send: value > 56 <87> pop > 57 <45> pushLit: Processor > 58 <D4> send: terminateActive > 59 <7D> blockReturn > 60 <D2> send: asContext > 61 <45> pushLit: Processor > 62 <D6> send: activePriority > 63 <F0> send: forContext:priority: > 64 <69> popIntoTemp: 1 > 65 <11> pushTemp: 1 > 66 <D7> send: resume > 67 <87> pop > 68 <11> pushTemp: 1 > 69 <7C> returnTop > ' > > > On 29 Sep 2010, at 20:29, StÃ©phane Ducasse wrote: > >> and http://code.google.com/p/pharo/issues/list?cursor=2818 >> >> Stef >> >> >>>> spawn: aBlock >>>> "Answer an ErlProcess running the code given in the parameter. The process isscheduled." >>>> | proc | >>>> <primitive: 19> "Simulation guard" >>>> proc := Process >>>> forContext: >>>> [1 halt. aBlock value. >>>> Processor terminateActive] asContext >>>> priority: Processor activePriority. >>>> proc resume. >>>> ^ proc > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] About open lively community vs a closed, withdrawn group of programmers
by Simon Denier Sept. 29, 2010

Sept. 29, 2010

Through Laurent Laffont's tweet 7:47 PM Sep 23rd Worth the read: "Leaving .net" http://whatupdave.tumblr.com/post/1170718843/leaving-net -- Simon

2 1