Please bear in mind that there are several thousand subscribers to
the Cocoa-dev list, including many Apple engineers. Every post in
effect costs the Cocoa community hundreds of dollars to process (and
takes time away from the engineers who might be working on the fix to
your bug!).
In 2005, over 26,000 messages were sent to the list. In order to
keep the list useful and to maximise your chances of getting an
answer to your question, please stay on topic and adhere to the
guidelines given in:
Remember you can also view and search the documentation in Xcode --
see the "Help" menu. You can see all the methods associated with a
class (and links to relevant documentation) using Xcode's Class
Browser (see the Project > Class Browser menu item).
You can keep your local documentation up-to-date by using the
Documentation update preference in Xcode. Apple's developer
documentation is updated en bloc about once a month. An update
package is made available at about the same time that updates are
published on the web site.
Developers are strongly discouraged from attempting to reformulate
Cocoa's memory management rules in posts to the list. Almost
invariably, someone makes a subtle or not-so-subtle mistake which
then results in confusion and additional messages to resolve the
issue. Simply post links to the relevant documentation, such as:
<http://developer.apple.com/documentation/Cocoa/Conceptual/
MemoryMgmt/Tasks/MemoryManagementRules.html>
"UNOFFICIAL Cocoa-dev Frequently Asked Questions"
<http://www.alastairs-place.net/cocoa/faq.txt>
Especially useful for pointers to documents relating to
memory management
and book recommendations
Note that you should never post to the list any message that was
sent to you
privately unless you have the original author's permission.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden