• 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
Probably dumb question...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Probably dumb question...


  • Subject: Probably dumb question...
  • From: Jeff LaMarche <email@hidden>
  • Date: Mon, 1 Aug 2005 12:04:21 -0400

Apple / NeXT have done a pretty good job with using consistent naming conventions. I know there are a few instances where they've dropped the ball, but overall they are quite consistent.

Does anyone, then, know if there is a reason behind the fact that some classes that are implemented as singletons (e.g. NSFileManager) use a naming convention of

+(id)defaultXXXX;

while others (NSWorkspace, NSApplication) use

+(id)sharedXXXX;

It's not really important, I'm just curious if there's a difference in the way they chose to implement the singletons in these cases, or if it simply an example of a naming convention gaffe?

Thanks,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Probably dumb question...
      • From: Jim Hamilton <email@hidden>
  • Prev by Date: Re: Checking System Version
  • Next by Date: Re: NSLayoutManager Background Layout Crash
  • Previous by thread: Re: CoreData & Bindings: How to make a predicate search a to-many rel ationship
  • Next by thread: Re: Probably dumb question...
  • Index(es):
    • Date
    • Thread