Re: But is it Object-Oriented?

> >>BTW, Java is specified roughly in the same way, and uses the name 
> >>"compilation units" for "modules".
> >
> >And the significant difference is, of course, that Java doesn't use
> >a "compilation unit" for encapsulation - Java uses types (classes
> >and interfaces) for encapsulation. 
> >
> Right, but since you are supposed to have only one top-level class
> per compilation unit, the difference is somewhat blur.

Which means that the top-level class provides a syntactic boundary for
the "compilation unit" - no such boundary in Nice.

-snip-
> You might want different levels of 'privateness'. That could be
> handled by nested units. But I think maybe we could leave that for a
> later stage, don't you think?

Let's see if we can be a little more concrete: in the wiki example 

http://nice.sourceforge.net/cgi-bin/twiki/view/Doc/HelloSwtUserInterfaceExample

It wouldn't be unlikely that we'd decide to subclass HelloGoodbye and
override helloButtonSelected. This (helloButtonSelected) is a method
that seems like it should be private, it's only useful in this context
or maybe when we subclass - we'd probably make it protected in Java, 

What to do in Nice?

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click