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]
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 09, 1999 2:55 PM
Subject: [REBOL] RFF: empty? for blocks Re:(4)
> Now duly reported to feedback, with Larry's addendum.
>
> *********** REPLY SEPARATOR ***********
>
> On 12/9/1999 at 10:10 AM [EMAIL PROTECTED] wrote:
>
> Hi,
>
> what you uncovered here is very interesting indeed. Have you reported it
as a bug?
>
>
>
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Tel 716 425-0252; Fax 716 223-2506.
> -- http://www.husted.com/
>
>
>
