Re: Protecting memory
Re: Protecting memory
- Subject: Re: Protecting memory
- From: Alex Zavatone <email@hidden>
- Date: Wed, 18 Jul 2012 22:02:41 -0400
Mmmmmm, store it in a nonmutable array for the time being?
Just a wild guess.
Or store a flag/BOOL that says "I can or can not be modified".
Sorry if this has already been covered.
On Jul 18, 2012, at 9:54 PM, Charlie Dickman wrote:
> After initializing a necessarily mutable array is there any straightforward way to protect it from being modified?
>
> The only way I can think of is to write the initialized mutable array to a file and then initialize a non-mutable array with the contents of the file and then using the non-mutable array instead of the mutable one.
>
> Charlie Dickman
> email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden