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@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@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@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of James Ladd [james_ladd@hotmail.com] Sent: Wednesday, September 29, 2010 6:28 PM To: pharo-project@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project