Hi guys,
Damien, Alexandre:
>>> I am aware that I am talking as someone who does not maintain cross-
>>> dialect applications, but we cannot trade readability for a local in
>>> time commodity.
>> Sure, but we could try to make the transition easier (e.g., complain
>> to Janko for the moment and wait until Pharo stable to enforce
>> conventions)
Stéphane Ducasse wrote:
> Yes I contacted Janko if he can fix that
I can fix of course but I'm a bit surprised that in Squeak the class
variables are supposed to be lower case. I have in mind back from 1996
that they must be uppercase.
I just managed to open an old VisualWorks 2.5.2 image back from 1996 and
exactly, class vars should be uppercase, see this class construction
template:
NameOfSuperclass subclass: #NameOfClass
instanceVariableNames: 'instVarName1 instVarName2'
classVariableNames: 'ClassVarName1 ClassVarName2'
poolDictionaries: ''
category: 'Collections-Unordered'
But naming them lowercase is not enforced, you just got a warning:
Static variable names should be capitalized.
So, it seems that Squeak changed this convention or is this just a
consequence of some later developed habit?
From this I suggest that Lucas's proposal is considered, but only for
this case regarding the class variables. Otherwise we will have the
porting problems all the time.
Best regards
Janko
--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
