• 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: List Question: Can someone explain this to me?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: List Question: Can someone explain this to me?


  • Subject: Re: List Question: Can someone explain this to me?
  • From: Jon Pugh <email@hidden>
  • Date: Fri, 14 Jun 2002 08:33:09 -0700

At 12:27 PM +0100 6/14/02, Nigel Garvey wrote:
>It makes sense (and sounds easier to implement) if 'copy' *always*
>duplicates data and creates new pointers, while 'set' only duplicates
>pointers to existing data. It *doesn't* make sense for 'copy' to behave
>like 'set' with simple data but then do something quite different with
>compound data.

It's the other way around. Copy always copies data, not pointers. Set copies data sometimes and copies pointers the other times. I'm not certain of the exact rules, as I mentioned, they changed numerous times during development as Warren realized there were new cases where set should behave more like copy.

Personally, I almost always use set and seldom use copy, except when dealing with lists, as this is the place where set will normally bite you.

Jon
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: List Question: Can someone explain this to me? (From: Nigel Garvey <email@hidden>)

  • Prev by Date: Re: OS X: determine if Explorer is Classic
  • Next by Date: Re: OS X: determine if Explorer is Classic
  • Previous by thread: Re: List Question: Can someone explain this to me?
  • Next by thread: URL Access Scripting problem
  • Index(es):
    • Date
    • Thread