As a general rule, you want to avoid attempting to name classes with such generic names. It makes you very much more likely to end up with a class name conflict somewhere, especially in large projects. Classname prefixes are usually what's used to help ensure there are no such conflicts.

- Bryan

On Sep 30, 2009, at 1:11:06 PM, Alex Reynolds wrote:

On Sep 30, 2009, at 4:04 AM, I. Savant wrote:

Whatever the answer, the simple solution is to change your entity's name.

Unfortunately, that simple solution means parting ways with the naming scheme of the source I'm pulling data from and changing the naming scheme for all my other entities/classes, too, which I was hoping to avoid. But thanks to all for the confirmation.

-Alex

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/bryanhenry%40mac.com

This email sent to bryanhe...@mac.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to