• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Protecting memory
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Protecting memory


  • Subject: Re: Protecting memory
  • From: David Duncan <email@hidden>
  • Date: Wed, 18 Jul 2012 19:01:01 -0700

On Jul 18, 2012, at 6:54 PM, Charlie Dickman <email@hidden> wrote:

> After initializing a necessarily mutable array is there any straightforward way to protect it from being modified?

-copy will give you an immutable instance.

> 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

--
David Duncan


 _______________________________________________
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

References: 
 >Protecting memory (From: Charlie Dickman <email@hidden>)

  • Prev by Date: Protecting memory
  • Next by Date: Re: Protecting memory
  • Previous by thread: Protecting memory
  • Next by thread: Re: Protecting memory
  • Index(es):
    • Date
    • Thread