>
> Way Back When, I went through a similar confusion of properties and
> symbols--like Ramesh appears to have done, I wasn't sure how they fit
> together. Property lists always have symbols (at least in the books I
> read), so the # must indicate a property, right?
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.
>
> I've done my time as a teacher,
I can relate to that. I am a trained teacher and have been teacing Director and Lingo
for about 5 years now so I fully understand what You�re trying to do, and I do agree
on the concept of taking small steps into the jungle.
Take care
BTW - anyone planning on joining Macromedu UCON 2001 in April. Maybe we should have a
huge Lingo-l party (or am I kicking in a wide open door here??)
Bjarne
_______________________________________________________
If it's true that we are here to help others, then what exactly are the OTHERS here
for?
Bjarne Nyquist
Researcher, Lingo Programmer
The Interactive Institute, phone: +46-(0)8 783 24 74
www.interactiveinstitute.se
[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!]
