Re: bogus retain via NSEnumerator

[Michael Ash]

On Sun, 2 May 2004, Uli Kusterer wrote:

> In article <20040420154904.V14240@agamemnon.twistedsys.net>,
>  Michael Ash <mike@mikeash.com> wrote:
>
> > Any object you get back from a method that's not "alloc", "copy", or
> > "retain" (plus the variants like mutableCopy) is autoreleased.
>
> Danger, Will Robinson!
>
>  This is a rough guideline for use, but not quite correct.
>
>  Actually, the only guarantee you get is that you're not responsibe for
> releasing it if there's no "alloc", "copy", "retain", "load" or "new" in
> the name (load is a special case, but worth mentioning if you're
> manually loading NIBs).
[snip rest of explanation]

You are, of course, completely right. Thanks for the clarification.