> Ladislav wrote:
> =================
> did anyone report The following?
>
> >> head insert copy [] ()
> == [unset]
> >> change copy [1] ()
> ** Script Error: change is missing its value argument.
> ** Where: change copy [1] ()
>
> =================
>
>> ()
>> type? ()
== unset!
>> copy [()]
== [()]
>> compose copy [()]
== []
>> first compose copy [()]
** Script Error: Out of range or past end.
** Where: first compose copy [()]
well, compose seems to turn () in a block into literally nothing, not unset!,
so which do you think is right, the insert that sticks an unset value into the
block,
or the copy which refuses to change 1 to nothing at all?
Is there some great use to having unset in a block ?
Or were you just saying the two should behave consistently but don't?
-galt
