- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12159
by Marcus Denker Sept. 30, 2010

Sept. 30, 2010

12159 ----- Issue 3018: DisplayScreen is missing Tiny class variable Issue 3017: UpdateStreamer is missing saveLocally instance variable Issue 3016: ParseNodeEnumerator is missing theSelectBlock instance variable Issue 2813: MailSender is not deployable -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

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

Sept. 30, 2010

12158 ----- - Issue 2996: Base64MimeConverter with multiline option. Thanks dik :)

1 0

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

Sept. 30, 2010

12157 ----- - Issue 3019: add instance side methods to PackageInfo and SystemOrganizer. - Issue 2995: PharoKernel Part 19.

1 0

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

Sept. 30, 2010

12156 ----- - Issue 2993: PharoKernel Part 17. Thanks Pavel and Nicolas :) Stef and nicolas

1 0

[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

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