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
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
