Alan Burlison wrote: > Branden wrote: > > Any suggestions? > Yes, but none of them polite. > You might do well to study the way perl5 handles these issues. Perl 5 basically clones on every assignment. As it uses refcounting, it knows it doesn't need to clone a string if its refcount=1 and it's marked as temporary, i.e., only a temporary that will go away anyway knows about this string, so it's guaranteed no other reference to it will exist. - Branden
- 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