[REBOL] Re: Bug! in assignment to date! values with stacked set-path values
From: rotenca:telvia:it at: 14-Nov-2002 12:22
Hi Ladislav,
> You are right. The behaviour can be corrected, although that might influence
> the speed of the interpreter...
Yes, but func are already fetched twice, why not path?
> When we are at it, we shall ask RT to change the path business more
> thoroughly to introduce referential transparency. I am afraid, that this
> change will affect the way Rebol parser (make block! / load) works, because
> I would suggest to not treat #"(" and #")" as ordinary delimiters. Instead
> Rebol should treat them as "forbidden" characters, which aren't allowed to
> occur in words.
I don't undertand well why. Can you make an example?
> Nevertheless,
>
> a/(1 + 2)
>
> should differ from
>
> a / (1 + 2)
>
> , where the former can be treated as a path, while the latter as an
> expression, which divides A by 3.
>
> What do you think about the fact, that the difference is small, which may
> lead to confusions?
the problem is general. Many cases in Rebol are of this nature:
2/ 1
2 / 1
2 /1
---
Ciao
Romano
