Stef, 

I have been making a lot of use of SIF.  There are some silly problems with 
method categories that I have learned to remember (the hard part<g>) to fix 
using even search and replace, but I have also done some "refactoring" using 
the regex package and match/replace.

Assuming you have an image with offending code, an expression that matches an 
isolated $_ (white space on either side) migh be able to fix assignments by 
replacing the matches with :=.  It might be useful on its own, and it brings up 
another proposed solution, which is to optionally treat isolated underscores as 
assignments, and to treat them as part of identifiers when not bracketed on 
both sides by whitespace (from Gemstone??).

Bill



-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Stéphane 
Ducasse
Sent: Friday, November 13, 2009 8:12 AM
To: [email protected]
Subject: Re: [Pharo-project] Status about compiler _ changes


On Nov 13, 2009, at 1:16 PM, Lukas Renggli wrote:

> As far as I remember from the other mail-thread there was consensus to 
> allow underscores in identifiers and get rid of underscores in 
> assignments. What is unclear for me is how we want to proceed and when 
> to integrate it?
> 
> 1. Do we just change the scanner for 1.1 without fallback?
> 
> 2. Do we add a setting (fix the existing setting) so that the scanner 
> can be changed on demand?
> 
> I prefer 1, because it is simpler and does not allow the system to be 
> in an inconsistent state. 2 is more convenient for people, because 
> they can change the setting to load old code, fix the code and change 
> the setting back. Potentially that leaves the system in an 
> inconsistent state though.

2 would be nice because as integrators we could make sure that the code is in 
consistent state even with pain. 

Now could not we have 3?
        3 
        do 1 (ie no preference) but transform the code from _ into := 
automatically.
It would be really great in fact

Stef

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to