Private Names and Methods

Kevin Smith khs4473 at
Thu Apr 5 09:29:33 PDT 2012

> On the other hand, private names are incredibly flexible in that you can
> easily implement any kind of “friend” (à la C++) scheme, simply by passing
> the name to all parties that should know about it. That means that you can,
> say, implement a “layer” where one fragment (=set of methods) per class
> among a set of classes communicates via a private protocol.

I'm not addressing the usefulness of private names for other situations.  I
am stating that they are not appropriate for refactoring out common code
within a class.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list