Re: File Extensions Problem
Re: File Extensions Problem
- Subject: Re: File Extensions Problem
- From: "R.L. Grigg" <email@hidden>
- Date: Wed, 27 Aug 2008 11:50:08 -0700
On Aug 22, 2008, at 4:24 PM, Thomas Engelmeier wrote:
Am 22.08.2008 um 17:23 schrieb Michael Ash:
On Fri, Aug 22, 2008 at 6:23 AM, Graham Cox
<email@hidden> wrote:
safe to delete items in the array at or higher than the current
index. By
the definition of an array, removing an item only affects the
indexes of
objects with equal or greater indexes than the removed item.
You are making a big, unwarranted assumption about how
reverseObjectEnumerator works. Namely, you are assuming that it
merely
tracks an index, and uses -objectAtIndex: (or equivalent) to retrieve
each object.
actually, there was an extensive thread last year. It seemed each
enumerator created surprisingly a copy of the array, giving the OP
some memory (or performance?) related trouble. IIRC it was the
combination of a tight loop with tons of enumerators w/o local
autorelease pools. Fast enumerators probably changed the rules since
Tiger.
This is interesting. Correct me if I'm wrong but as a newb what I'm
getting from all this is if I design my code around implementation
specifics of frameworks or even the language I'm using, that equates
to a unrobust design, cuz if the underlying implementation changes,
I'm screwed, whereas simpler, more bread-and-butter "textbook" designs
are much more likely to weather any underlying implementation changes,
sort of like keeping your design at a high level and not dirtying it
with low-level implementation specifics.
Is that a reasonable conclusion to draw?
Thx,
Russ
_______________________________________________
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