Re: Is this a bug?

Hi,

> Essentially, a class B inheriting from a class A can access A's private 
> methods, but only if class A is defined in the same file as class B. Is this 
> deliberate?

Yes, this is the meaning of 'private' in Nice.

> If so, is there anything akin to a "protected" keyword in Nice?

Not at the moment. How would it be defined? (keep in mind that multi-methods 
do not "belong" to classes)

One possible new visibility would be methods that can be overwritten but not 
called. This would allow leaving an implementation open, while stating that 
this method is not meant to be called directly.

Cheers,

Daniel


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf