Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Class naming convention



What IDE are you using?

If you use a good IDE like Eclipse, the directory organization doesn't matter much, since you never see it. Xcode lets you put things where you want, but in my experience, it eventually bites you because other things in the java world expect the directory path == class path paradigm.

I used to ignore classpaths - now I participate fully.

Ken

On Aug 30, 2006, at 4:02 PM, bsd5tu1 wrote:

How many out there really adhere to the class naming convention (example com.mycompany.myproduct.XXX.java) for actual products? Why or why not?

I've always disliked using packages when possible because to me it seems Java ties the package with a directory structure too tightly. Sometimes I like to arrange things in order to just "tidy up" things but doing so often ends up causing packaging problems.

Just curious,

Thanks in advance.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Java-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden
References: 
 >Class naming convention (From: bsd5tu1 <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.