[Sorry, I changed the subject back, because I want to reply about Variables]
Torsten Anders writes: > > On 14.03.2006, at 17:02, Andreas Franke wrote: > > Torsten Anders wrote: > >> Still, what is gained if you are allowed to replace _/*SomeThing*/ by > >> _SomeThing, in case the latter is equivalent to _? > > Four characters. If you operate on an 80-chars-per-line style for > > source code, that's significant :-) > > I would always hesitate before extending the core of Oz. Is it really > worth to extend the Oz syntax to save these four characters (in case _X > is equivalent to _) or even to introduce some slight semantical variant > (in case _X is a special form of X which does not trigger certain > warnings)? > Nobody has argued for allowing _X to be equivalent to _. Since having _X as a special form of X which does not trigger certain warnings would require extending the language (to allow Variables to start with an underscore) then I think this would require someone to produce a Mozart enhancement Proposal (MEP). So far there doesn't seem sufficient support for this, but if there are people out there who like it, hate it, or would propose an alternative, please make your feelings known! k [Adding a compiler option to report shadowed variables doesn't require a MEP even though it might be made the (noisy) default, I hope!]. _________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
