Issue status update for
http://smalltalk.gnu.org/project/issue/286
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/286
Project: GNU Smalltalk
Version: <none>
Component: VM
Category: bug reports
Priority: normal
Assigned to: Unassigned
Reported by: dpollet
Updated by: bonzinip
Status: active
I agree that it's confusing, but "stealing" a binding from Undeclared
would not be possible for two reasons:
* you risk introducing a binding from one class to another
* you cannot handle the case in which two different classes have
the same undeclared variable, and then the variable turns out to be a
class variable /only in one of the two/.
The way to fix this would be to give a warning upon defining the class
variable if the variable can be found in Undeclared. Usually the
naming conventions for globals and class variables are different enough
that it should not give many false positives.
_______________________________________________
help-smalltalk mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
