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

At 11:14 AM -0400 8/31/06, Rick Genter wrote:
On 8/30/06, bsd5tu1 <email@hidden> 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?


At work we use it extensively. It's important when you start working
with multiple third-party libraries. And with a decent IDE, the
directory structure is not an issue, and the package structure can be
a benefit.

The package structure also helps you to minimize the "surface area" of
the API of your app, through the use of package-private classes and
methods.

Even when working on personal projects, packages are a very valuable organizing tool.

If you looking in any of my projects, you would not just see
com.myname.project.XXX.java but
com.myname.project.packagea.packageb. ... .xxx.java

For example I have packages for menus, ui, utility, db, files, etc. Within those I may have more specialized packages with classes all up and down the package tree as needed.

_______________________________________________
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>)
 >Re: Class naming convention (From: "Rick Genter" <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.