You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The end of the 'Class variables' section used the ColorNames class variable as an illustration of the shared nature of class variables. In Pharo 4, ColorNames has been replaced by ColorRegistry.
Which is fine, I changed the example to refer to ColorRegistry. But the last paragraph (currently commented out, see lines 1072-1074), mentioned that ColorNames is accessed from the instances of Color. Whereas the new ColorRegistry is primarily used by class methods in Color.
My question is, should we:
Just omit that last paragraph, since we made our overall point without it
Use some other class variable of Color
Use a class other than Color (since in 4, it doesn't have any subclasses, for example) and another class variable?
The end of the 'Class variables' section used the
ColorNames
class variable as an illustration of the shared nature of class variables. In Pharo 4,ColorNames
has been replaced byColorRegistry
.Which is fine, I changed the example to refer to
ColorRegistry
. But the last paragraph (currently commented out, see lines 1072-1074), mentioned thatColorNames
is accessed from the instances ofColor
. Whereas the newColorRegistry
is primarily used by class methods in Color.My question is, should we:
/cc @Ducasse
The text was updated successfully, but these errors were encountered: