Re: NSString's "mutableCopy" creating a leak?
Re: NSString's "mutableCopy" creating a leak?
- Subject: Re: NSString's "mutableCopy" creating a leak?
- From: Brian Stern <email@hidden>
- Date: Wed, 1 Oct 2008 22:46:34 -0400
Hi All,
Just a note. Although the moderator doesn't wish to see discussion of
list issues here he should be prepared for dozens, probably hundreds
of questions here where the answers to the questions go something like
"you can't send dealloc to objects", "you can't call drawRect from
your code directly", "you can't draw from a secondary thread' and many
more like that. Perusal of the message boards that have grown up
around iPhone development reveals lots and lots of questions along
those lines.
While the lists here are Apple's, they exist and are valuable because
we all contribute to them.
Scott, and the other moderators: I'm sorry that your management has
failed you and not given you guidance about what was going to happen
today and what you should do on this list regarding iPhone questions.
However, everyone on this list moves on internet time. Apple needs to
keep up. The time to decide what new lists should exist is quickly
passing. The people that this affects most are the subscribers to
this list and we should have a say in what happens.
It sounds like the lawyers are still in charge.
--
Brian Stern
email@hidden
_______________________________________________
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