[REBOL] Re: Bug! in assignment to date! values with stacked set-path values
From: lmecir:mbox:vol:cz at: 18-Nov-2002 13:09
Hi Romano,
> > Nevertheless, paths can be evaluated like above and it makes perfect
sense
> > to me:
>
> Do you means that set-path should be fetched only one time?
I mean, that paths should be evaluated differently, than set-paths (the
order of evaluation should be different for these two datatypes).
> I think that the problem with path could arise from the fact that set-path
> does not exists as true datatype!, it is only the last item in the path
that
> make rebol thinks it is a set-path.
I don't agree with that, every Rebol datatype has got a type attribute
attached to it, IMO.
> The result is a strange behaviour: a set-path which works like a path
>
> x: func [/b][3]
> type? first [x/b:];== set-path!
> x/b: ;==3
This is unexpected, but it may be justified as an attempt to "do something
meaningful" instead of firing an error.
> Another strange thing:
> :x ;== function?
> :x/b ;== 3
This is consistent with something like a/:i, when the interpreter considers
such a thing to be a path:
type? first [:x/b] ; == path!
Ciao
-L
