• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Convention for class name prefixing . . .
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Convention for class name prefixing . . .


  • Subject: Re: Convention for class name prefixing . . .
  • From: Kyle Sluder <email@hidden>
  • Date: Thu, 16 Jul 2009 10:25:06 -0700

On Thu, Jul 16, 2009 at 9:14 AM, Michael A.
Crawford<email@hidden> wrote:
> So, what is the convention?  I assume I should prefix my class names so that
> I minimize potential for name space conflict, but what should I use as a
> prefix?  The options readily available to me are:

Choose whatever makes you happy that isn't going to conflict with
other things.  You might want to use separate prefixes per project so
that if you start sharing code between them you don't cause a
conflict.

> I'm used to namespaces, which I use in C++ and used to use when writing C#
> code.

Please join in the enhancement requests.  The lack of ObjC namespaces
is more than frustrating.

--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Convention for class name prefixing . . . (From: "Michael A. Crawford" <email@hidden>)

  • Prev by Date: Re: Problems displaying an image in UIWebView [solved]
  • Next by Date: Sending actions with a custom NSControl subclass
  • Previous by thread: Convention for class name prefixing . . .
  • Next by thread: Sending actions with a custom NSControl subclass
  • Index(es):
    • Date
    • Thread