UNSET
[1/3] from: ptretter:norcom2000 at: 14-Jan-2001 19:06
Does UNSET? current have a bug. Look at the following:
>> unset 'a
>> print a
** Script Error: a has no value.
** Where: print a
>> blablablah: 2
== 2
>> unset 'blablablah
>> print blablablah
** Script Error: blablablah has no value.
** Where: print blablablah
>> unset? 'blablablah
== false
>> print blablablah
** Script Error: blablablah has no value.
** Where: print blablablah
>>
hmmm..... I'm scratching my head.... Hopefully this is a bug. Now this.
>> not unset? 'blablablah
== true
>> value? 'blablablah
== false
>> value? blablablah
** Script Error: blablablah has no value.
** Where: value? blablabla
Any thoughts...
Paul Tretter
[2/3] from: jeff::rebol::net at: 15-Jan-2001 13:22
Howdy, Paul:
This might be a good FAQ.
UNSET? asks if the datatype is unset!
When you do:
unset? 'some-word
it says, "why no, 'some-word is a word!, not an unset!"
Try:
unset? get/any 'blablablah
-jeff
[3/3] from: ptretter:norcom2000 at: 15-Jan-2001 15:56
LOL! Jeff,
I like the way your personified your response. That helps, thanks. I
was basing my understanding off the supplied help within the function.
Paul Tretter