On Sat, 10 Feb 2001, Buddha M Buck wrote: > I think what he's thinking (in C terms) would be more like the following: Right. It already has a technical name - copy-on-write. I should have made it more clear that I recognized the intended mechanism. I was trying to demonstrate that Perl-level mechanisms already existed to do value aliasing. I was also trying to show that what he is suggesting is a lot like aliasing with some simple copy-on-write STORE magic. For some reason I thought that by pointing that out I could relieve him of his bizarre worries about garbage collecting things with references. I probably should have just gone to bed instead. -sam
- GC: what is better, reuse or avoid cloning? Branden
- Re: GC: what is better, reuse or avoid cloning? Sam Tregar
- Re: GC: what is better, reuse or avoid cloni... Buddha M Buck
- Re: GC: what is better, reuse or avoid c... Sam Tregar
- Re: GC: what is better, reuse or avoid cloning? Alan Burlison
- Re: GC: what is better, reuse or avoid cloning? Dan Sugalski
- Re: GC: what is better, reuse or avoid cloning? Filipe Brandenburger
- Re: GC: what is better, reuse or avoid cloning? Branden
- Re: GC: what is better, reuse or avoid cloni... Jan Dubois
- Re: GC: what is better, reuse or avoid c... Branden
- Re: GC: what is better, reuse or avo... Dan Sugalski
- Re: GC: what is better, reuse o... Branden
- Re: GC: what is better, reu... Dan Sugalski