[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


   > From: Morgan McGuire <morgan3d@yahoo.com>
   > Copy-on-mutate is a form of lazy evaluation.  It means that:
   > A = B
   > doesn't actually copy the values from B into A (A and B are values, not
   > pointers), instead it just remembers that A is supposed to be equal to
   > B.  This saves memory and time.

Under what circumstances should a language implementor *not* use
copy-on-mutate?  Where's the cost?

"[N]ine times out of ten, in the arts as in life, there is actually no
truth to be discovered."  --H. L. Mencken
== Seth Gordon == sethg@ropine.com == http://ropine.com/ == std. disclaimer ==