<html><body>
<p>+1<br>
But you may eventually need some kind of visual indicator in the browser showing what prefs were in place when the method was compiled.<br>
Yuck.<br>
<br>
Excellent job of handling the issue though.<br>
Regards,<br>
Sam<br>
<br>
<br>
Sam S. Adams, IBM Distinguished Engineer, IBM Research<br>
Mobile: 919-696-6064, email: ssadams@us.ibm.com<br>
Asst: Kenndra K. Quiles. (732) 926-2292 Fax: (732) 926-2455, email: Kenndra@us.ibm.com<br>
<<Hebrews 11:6, Proverbs 3:5-6, Romans 1:16-17, I Corinthians 1:10>><br>
<br>
<br>
<tt>squeak-dev-bounces@lists.squeakfoundation.org wrote on 03/12/2010 11:14:49 PM:<br>
<br>
> Andreas Raab <andreas.raab@gmx.de> </tt><br>
<tt>> Sent by: squeak-dev-bounces@lists.squeakfoundation.org<br>
> </tt><br>
<tt>> 03/12/2010 11:14 PM</tt><br>
<tt>> <br>
> Please respond to<br>
> The general-purpose Squeak developers list <squeak-<br>
> dev@lists.squeakfoundation.org></tt><br>
<tt>> <br>
> To</tt><br>
<tt>> <br>
> The general-purpose Squeak developers list <squeak-<br>
> dev@lists.squeakfoundation.org></tt><br>
<tt>> <br>
> cc</tt><br>
<tt>> <br>
> Subject</tt><br>
<tt>> <br>
> [squeak-dev] Selectors with underscores: Have your cake and eat it, too...</tt><br>
<tt>> <br>
> Folks -<br>
> <br>
> Attached my take on selectors with underscores. It basically separates <br>
> the issue of using underscores in assignment from the issue of using <br>
> underscores in selectors, puts this into two individual preferences, and <br>
> allows per-class scoping while providing a system-wide default.<br>
> <br>
> The possible combinations of preferences are:<br>
> <br>
> * allowUnderscoreAssignments off, allowUnderscoreSelectors: off<br>
> The use of underscores is forbidden, i.e., the Croquet model.<br>
> <br>
> * allowUnderscoreAssignments on, allowUnderscoreSelectors: off<br>
> The classic Squeak usage; all of the following are assignments:<br>
> <br>
> a _ b => a := b<br>
> b_ c => b := c<br>
> d _e => d := e<br>
> f_g => f := g.<br>
> <br>
> * allowUnderscoreAssignments off, allowUnderscoreSelectors: on<br>
> The standard usage in other dialects<br>
> <br>
> a _ b => ((a) _) b<br>
> b_ c => (b_) c<br>
> d _e => (d) _e<br>
> f_g => (f_g)<br>
> <br>
> * allowUnderscoreAssignments on, allowUnderscoreSelectors: on<br>
> The hybrid usage requiring spaces around underscore for assignment:<br>
> <br>
> a _ b => a := b<br>
> b_ c => (b_) c<br>
> d _e => (d) _e<br>
> f_g => (f_g)<br>
> <br>
> This gives us a range of options to decide how to deal with it. I would <br>
> personally say that for the core image we should go with the first <br>
> option (disable underscores altogether) and only enable whichever option <br>
> we like for the release.<br>
> <br>
> What do people think about this approach? I think it provides the most <br>
> options and gives us ample flexibility to decide what we'd like to use <br>
> down the road.<br>
> <br>
> If there is no fundamental opposition I'll push it into the trunk in a <br>
> couple of days.<br>
> <br>
> Cheers,<br>
> - Andreas<br>
> [attachment "Underscores.2.cs" deleted by Sam Adams/Raleigh/IBM] <br>
</tt></body></html>