Jakob Hede Madsen wrote > Even scripts are actually sort of "instances" themselves, and does > everything regular instances does, including holding properties and > existing outside the scope of their "parent-member".
Yes, you're right - scripts can hold properties (I'm sure I did some experiments in the past and wasn't able to store values in 'uninstantiated' scripts beyond the life of the originating handler). > I'll try to explain a bit, but when you start to refer to scripts as > "instances themselves", the terminology becomes quite awkward, I > guess there would be real OOP terminology for this... but for now, > please bear with me. Don't worry, it was well explained. But perhaps Director needs its own OOP terminology. Perhaps "Primative objects" for things like Scripts, to help distinguish them from objects instantiated from scripts. > But of course, I understand what you mean by the term 'uninstantiated > script', and frankly this issue makes me feel that my vocabulary is > woefully inadequate... at least for any 'pedagogical' purposes... ;-) Well, I'll take your epistimological soundness over any pedantic pedagogical purpose... it helps to keep me ontologically grounded ;) Luke [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/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!]
