[REBOL] Re: Bug! in assignment to date! values with stacked set-path values
From: carl:cybercraft at: 12-Nov-2002 23:31
It's not just dates Andrew...
>> a: 1.2.3
== 1.2.3
>> a/1: a/2: 4
== 4
>> a
== 4.2.3
Carl.
On 12-Nov-02, Andrew Martin wrote:
> Here's an example:
>>> x: now/date
> == 12-Nov-2002
>>> x/day: 1 ; Try individually; OK!
> == 1
>>> x
> == 1-Nov-2002
>>> x/month: 1 ; Try individually; OK!
> == 1
>>> x
> == 1-Jan-2002 ; And the expected value is shown.
>>> x: now/date ; Get fresh value.
> == 12-Nov-2002
>>> x/month: x/day: 1 ; Now stack up the assignments.
> == 1 ; correct value is returned, but...
>>> x
> == 12-Jan-2002 ; Note that only the MONTH is altered...
>>> x: now/date ; Get fresh value.
> == 12-Nov-2002
>>> x/day: x/month: 1 ; Reverse the order....
> == 1
>>> x ; Note that only the DAY is altered...
> == 1-Nov-2002
> It's buggy on Rebol/Core, Rebol/View, Rebol/Base and all the beta
> versions.
> The work around for now is to separate the assignments, as shown in
> the first few steps.
> I've just sent this in to feedback.
> Andrew Martin
> ICQ: 26227169 http://valley.150m.com/
> -><-
--
Carl Read
