• 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: [[NSFileManager alloc] init] considered thread-safe
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [[NSFileManager alloc] init] considered thread-safe


  • Subject: Re: [[NSFileManager alloc] init] considered thread-safe
  • From: Michael Ash <email@hidden>
  • Date: Fri, 14 May 2010 16:57:51 -0400

On Fri, May 14, 2010 at 4:46 PM, Ken Ferry <email@hidden> wrote:
>> Regarding that 10.5 singleton safety bug, is this documented anywhere?
>> It seems like there are a lot of minor bugs which get fixed in later
>> OS revisions but persist in earlier ones that we often have to support
>> for a while. There are often easy workarounds like this, but we don't
>> find out they're necessary until we happen, by chance, to say the
>> right thing to the right Apple engineer on a mailing list.
>>
>> I know Apple documentation concentrates heavily on the latest release,
>> and with good cause, but it would be great if little stuff like this
>> could make it in somewhere. I don't know if you're the right person to
>> say this to, but I figured I'd mention it just in case.
>
> There's the release notes, but they're already long enough to put people
> off, and we do actually want everyone to read those.  I don't think this one
> made the notes, which was probably a fair decision - I'm not sure anyone has
> ever hit it in practice.  It was noticed in code inspection.

It does seem like a bug that would be pretty hard to hit. I'd say that
something like this ought to be in the docs for +defaultManager, as a
brief note. Maybe Xcode could get fancy and let you configure the docs
to only show what's relevant to your target OS, so people who target
10.6 don't have to see notes that only apply to 10.5. Now we're
*really* getting out of your area....

> Anyway, noted, though yes, I'm not a terribly helpful person to tell about
> it. :-)
> (I didn't do any of this work, by the way, just relaying it.)

I appreciate the relay. As for not being helpful, I figured I could at
least inject something into the collective Apple subconscious.

Mike
_______________________________________________

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: 
 >[[NSFileManager alloc] init] considered thread-safe (From: Quincey Morris <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Ken Ferry <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Quincey Morris <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Ken Ferry <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Michael Ash <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Jens Alfke <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Michael Ash <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Ken Ferry <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Michael Ash <email@hidden>)
 >Re: [[NSFileManager alloc] init] considered thread-safe (From: Ken Ferry <email@hidden>)

  • Prev by Date: NSDrawThreePartImage - Strange scaling behavior, is it supposed to do that?
  • Next by Date: Re: Looking for Cocoa Drawing Strategy Advice
  • Previous by thread: Re: [[NSFileManager alloc] init] considered thread-safe
  • Next by thread: NSSegmentedControl in a toolbar
  • Index(es):
    • Date
    • Thread