While I agree that org.webare is not too pretty, the reason to use org.webware or com.valinux as a class package hierarchy is to ensure that classes don't have naming conflicts by making the assumption that a top-level domain is unique which it is for all intensive purposes.
It's pretty common to have a DBPool class and if they're 5 people write them under the Webware package or the Webware.Database package, they'll overwrite each other and you wouldn't be able to switch between them if you wanted to.

Again maybe I'm missing something??? :-)

Mike
On Monday, October 28, 2002, at 02:46 PM, Ian Bicking wrote:

Someone has already noted that MakeAppWorkDir will help you (everyone
should use it really).  Webware does already have packages under
Webware/ -- Python packages are more casual than in Java (and a package
like org.webware is a serious faux pas in Python :)


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to