> If 'copy isn't used, b is another word pointing to the same data with a changed
>pointer.
Sounds like good advice, Russell. Though, this thread started because someone was
asking about using a second pointer to the same data, so copy would defeat that
purpose.
*********** REPLY SEPARATOR ***********
On 12/9/1999 at 4:05 PM [EMAIL PROTECTED] wrote:
These problems can be avoided by always using 'copy to create a new copy of
the original data.
>> a: [1 2 3 4]
== [1 2 3 4]
>> b: copy next a
== [2 3 4]
>> clear a
== []
>> next b
== [3 4]
>>
I've found this a good practice. If 'copy isn't used, b is another word
pointing to the same data with a changed pointer.
But it looks like a bug if clearing a doesn't also clear the pointer. Maybe
the 'clear operation doesn't clear the data but only affects the pointer?
Anyhow, 'copy is the way to avoid trouble, in my experience.
Russell [EMAIL PROTECTED]
