>I hope I didn�t intimidate any
> > one with my post.
Ok, I'm off work today and relaxed :-)
No, you didn't intimidate me. When I'm not clear in an explanation, I like
to know.
>I just find it important to be clear on
> > fundamentals when we go on to our different project issues.
Absolutely. I am guilty of a bit of obfuscation, I admit.
I've followed Ramesh's posts, and it looks to me like he's climbing the
learning curve--intelligent, inquisitive, but, like all of us at one time
or another, trying to get his arms around some unique concepts.
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?
I've done my time as a teacher, and I tried to put myself in Ramesh's
place, and explain it in the terms he appeared to be thinking. There's
plenty of time to learn about symbols--for now, I wanted to steer him in a
direction that made his code work.
I was a little fast and loose with the facts in my zeal to avoid a side
tour into data types. You caught me up on it, Bjarne, as I'm sure a number
of other experts did.
>put marker("start").ilk
>-- #integer
>(???)
Interesting that I read that just after making my post about using marker.
It appears that Director does resolve marker() to an integer.
That makes sense. Lingo is tokenized for runtime, so it's logical for the
pseudo-compiler to find the marker and substitute a frame number.
>put (True).ilk
>-- #integer
>put (False).ilk
>-- #integer
>(Huh?)
That makes sense also--true and false are just 1 and 0.
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!]
