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

Re: Probably dumb question...


  • Subject: Re: Probably dumb question...
  • From: Jim Hamilton <email@hidden>
  • Date: Mon, 1 Aug 2005 14:51:15 -0400


On Aug 1, 2005, at 12:04 PM, Jeff LaMarche wrote:

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;

This answer is going to be worth what you paid for it. <wink>

It seems to me that the "shared" examples you gave (NSWorkspace and NSApplication) really are singletons; I can think of at least a couple of "default"s (+[NSNotificationCenter defaultCenter], + [NSConnection defaultConnection]) that are NOT singletons.

As for +[NSFileManager defaultManager], you've got me...

Jim H
--
Jim Hamilton

email@hidden
email@hidden

_______________________________________________
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


References: 
 >Probably dumb question... (From: Jeff LaMarche <email@hidden>)

  • Prev by Date: Re: NSMutableSet funny
  • Next by Date: Re: menu item alignment question
  • Previous by thread: Probably dumb question...
  • Next by thread: Re: NSLayoutManager Background Layout Crash
  • Index(es):
    • Date
    • Thread