Public/Private is not just a category, it is also a declaration of
what is the interface of the object.
As I said, it's not critical, but I've been working with and without a
"native" private method, and I prefer working with them.
Namespacing is a different animal, and not as simple to implement
Please keep Pharo simple, why do you need private methods...you can include
then in a protocol named private...other language have it...yes...next
addition will be namespaces...other...I don't know...at last we have Java
El jue., 19 ago. 2021 9:00, Richard O'Keefe escribió:
> Many years ago
Many years ago there was a proposal in the Squeak mailing list about enforcing
a naming convention, "pvt", I implemented that in my Smalltalk system. The
compiler enforces the rule that pvt.[A-Z].* message can only be sent to
(self|super) (basicNew|basicNew: n|new|new: n|pvtNew: n)?
in a class
