>Well, as a matter of fact I have sucessfully used both strings, integers
>and objects as properties in property lists. I don�t know if this is
>unconventional, but I do it from time to time. I realize that the use of
>integers as properties in a property list is not such a good idea. Just
>imagine myList[2] if myList = [2:34, 3:67], but its still perfectly legal
>Lingo. Strings work just fine as properties, as do objects, so I would
>still be strict and say that # indicates a symbol and nothing else.
No disagreements there--it's just a common perception that symbols and
properties are equivalent.
My guess is that people use symbols in property lists for speed. A symbol
gets tokenized, and it's a much quicker to match a symbol than a string.
That's what gives property lists their speed, as far as I know. I don't
know Director's guts well enough to speak authoritatively, but, as Spock
would say, it's only logical.
Feliz Navidad!
Cordially,
Kerry Thompson
Learning Network
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
