Re: Packages as first class entities

lorenzo wrote:

> - one/some classes could be tagged with a special keyword 
> (facade/component/?). These classes will act as bigger blocks, they 
> will read config files, open connections, create a lot of other 
> classes, etc.

Just one more thing.
If you choose to use a package as a component, and this should be the 
norm for component-like packages(*), you wont be able to use single 
classes from that package

import as component org.app.*;  //you can use only components from this 
package
import as library org.app.*;    //every single class


(*) Not all packages should be component like, some could be just 
"library" of classes. Like real classes vs utility classes (Collections, 
Math, ecc.). The more component-like packages the better.


I've not found much on google, yet, just this

The Next Move in Programming: A Conversation with Sun's Victoria 
Livschitz 
<http://java.sun.com/developer/technicalArticles/Interviews/livschitz_qa.html>



Bye

Lorenzo


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20