On 28-May-02, Charles wrote:
> That is rather odd. The function, I do not feel, should actually
> perform an operation on the argument being passed. At least, not in
> general. Same happens with 'lowercase'.
> Well, it answers the question I recall seeing about capitalizing:
>>> uppercase/par
No, I don't think it is a bug.
It is just like replace.
Just work on a copy of x:
y: uppercase copy x
And this is the same in the latest view beta I'm running.
Anton.
> >> x: "hello"
> == "hello"
> >> y: uppercase x
> == "HELLO"
> >> x
> == "HELLO" < Why is x now uppercase?
Hi,
> >> x: "hello"
> == "hello"
> >> y: uppercase x
> == "HELLO"
> >> x
> == "HELLO" < Why is x now uppercase?
>
> This is really unexpected behavior! Is this a bug?
No it is not a bug. It is actually a nice flexible design.
There are two things at work here.
(1)--
That is rather odd. The function, I do not feel, should actually perform an
operation on the argument being passed. At least, not in general. Same
happens with 'lowercase'.
Well, it answers the question I recall seeing about capitalizing:
>> uppercase/part x 1
;)
> Hi rebols,
>
> >> x:
