I think (I’m speculating, that is) that the confusion was due to the
unusual (but not incorrect) choice of having key/val pairs stored in symbol
property lists as

      +-----+-----+
      | VAL | KEY |
      +-----+-----+

where VAL is the the CAR position and KEY in the CDR position. There is not
right or wrong about this, that’s just how it works. I find this point very
interesting. I believe it has something to do with streamlining the
picolisp (C or asm) code regarding properties, but I don’t know for sure.
Alex?
​

Reply via email to