At 05:36 PM 8/8/00 -0400, Uri Guttman wrote: >but why reinvent the wheel with this code? we have modules which do >close to this now, and we have talked about using the GC traverse engine >as well. Yes, the code is only indirectly useful to the RFC since I expect it to be implemented internally (by someone else :-). But if it gets complicated to express certain aspects of the algorithm it may be handy to use the Perl version as pseudo-code to establish the intent of the RFC. -- Peter Scott Pacific Systems Design Technologies
- RFC 67 (v1) Deep Copying, aka, cloning around. Perl6 RFC Librarian
- Re: RFC 67 (v1) Deep Copying, aka, cloning aroun... Damian Conway
- RE: RFC 67 (v1) Deep Copying, aka, cloning around... Garrett Goebel
- RE: RFC 67 (v1) Deep Copying, aka, cloning ar... Peter Scott
- RE: RFC 67 (v1) Deep Copying, aka, cloning around... Garrett Goebel
- Re: RFC 67 (v1) Deep Copying, aka, cloning ar... Uri Guttman
- Re: RFC 67 (v1) Deep Copying, aka, clonin... Peter Scott
- Re: RFC 67 (v1) Deep Copying, aka, cl... Uri Guttman
- Re: RFC 67 (v1) Deep Copying, ak... Peter Scott
- RE: RFC 67 (v1) Deep Copying, aka, cloning around... Garrett Goebel
- Re: RFC 67 (v1) Deep Copying, aka, cloning ar... Jonathan Scott Duff
- Re: RFC 67 (v1) Deep Copying, aka, clonin... Dan Sugalski
- Re: RFC 67 (v1) Deep Copying, aka, cloning ar... Damian Conway