What is wrong with this picture ?
Click on the image to see it in full resolution.
I am not sure since when, but -[NSEnumerator nextObject] at least when enumerating an NSArray is returning an autoreleased object. Is this something new or has this been done since the dawn of time ? This
pisses me off annoys me greatly, because autoreleased objects make it harder for me to debug. I prefer my objects to dealloc as soon as possible, because if they fail, I have a useful stacktrace.
So I rewrote many of my non-critical loops to use the familiar for(;;) -[NSArray objectAtIndex:] "pattern". (I am surely not using Foundation code for any of my critical loops, he he)
The question I asked myself is this though.:Why is -NSArray objectAtIndex:] not returning an autoreleased object ? It is inconsequential to return an autoreleased object in -[NSEnumerator nextObject] but not in -NSArray objectAtIndex:].
Should I file a bug for orthogonality and misery ? I don't think so. Let sleeping poodles lie.
In other news, I have recently made a little change in the MulleAutoreleasePool, so this has to settle a little bit again before I can release it. Also I need to write an article around it and that takes time. Time is something I don't have too much of recently...