On Jul 17, 2009, at 9:30 PM, Cameron Sanders wrote:
> I just loaded the code I have been developing in Pharo into Squeak
> (closure VM, using 4.10.2-7179web09.07 image base) and it had one
> complaint while loading:
>
> Squeak (seemingly) requires an initial cap on class variable names.
> [Maybe it allows it... but it popped up the debugger on an MC load.]
This is fun because I thought only previous version of pharo were
doing that
> Does Pharo allow the symbol to start with lower case by design, or was
> that act of omission? I am merely raising point to make certain it is
> an act of commission.
We had discussion in the past.
class variables should be Uppercased
instance variables should be lowercased.
I believe that this is part of the semantics and that this is good
that the compiler
enforces that and reject bad code. Now since lukas complained loudly
we removed
the checks that we introduced earlier. People cannot say that we are
not open and listening.
Now the latest version allows you write any shitty code you want, to
the point that you can
totally confuse yourself by writing instance variable with Uppercase
and the inverse too.
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
