You can find many guidelines like these in the "Smalltalk with Style" book.
For instance on page 3 it says "Upper and lowercase letters also
distinguish variable scope. Variables beginning with an upper case letter
(globals, classes, *class variables*, and pool dictionaries) are global to
all meth
True, I already found few examples of accessors to class variables, but I
like to be sure when I use it for the first time. Thank you.
Jan
Christian Caldeiro wrote
> Class variables should be written with Uppercase (but there are some
> classes in Pharo that don't follow this convention). Class
Class variables should be written with Uppercase (but there are some
classes in Pharo that don't follow this convention). Class methods
(accessors in this case) are written in lowercase. Again, you can find
several samples in Pharo.
Thanks
Christian
On Tue, Apr 7, 2015 at 1:54 PM, Jan B. wrote:
Jan B. wrote
> Hello
>
> Class variable names should start with capital letter (as I just found
> out), like RecentProjects. We have a getter to it. Should such accessor
> method be named recentProjects or RecentProjects?
>
> ... class#>>(r/R)ecentProjects
> ^ RecentProjects
>
> Jan
--
Hello
Class variable names should start with capital letter (as I just found out),
like RecentProjects. We have a getter to it. Should such accessor method be
named recentProjects or RecentProjects?
... class#>>(r/R)ecentProjects
^ RecentProjects
Jan
--
View this message in context:
htt
