>> This behaviour seems a bit strange to me. I would expect (pack
>> (intern "NIL")) to return NIL...
> You are right. This is a bug in 'intern'.
> 'NIL', however, is a special symbol which is recognized by the
> reader. In 32bit PicoLisp, there is no symbol with a name "NIL"
> interned, so that when
> : (intern "NIL")
> is executed, a new symbol with that name is interned. Though it looks
> like the original 'NIL', it is a different symbol, which is neither
> "false" nor matches an empty list etc. This will create chaos during
> further execution.
Are there other "special" symbols in the 32bit PicoLisp that behave