Geoff Canyon wrote:
On Thu, Aug 8, 2013 at 8:01 AM, Timothy Bleiler wrote:
So, to the extent that it might effect preferences for the syntax, what
are some examples of how this would be used?
This seems similar to the distinction between class and instance methods.
Class methods are often used to store values that all the instances share
in common. In LC, a local variable in the behavior seems like the
reasonable way to handle this. For example, if you are writing Space
Invaders and need to keep track of how many invaders are left, a local in
the behavior script for the invaders would work.
Having the scriptObject would let you store properties on the behavior
object, which might come in handy if you want to save the stack? Not sure.
This raises an interesting question: What if you don't want to save
those values? Or what if the value you want to use is a nested array,
which is much slower to get in and out of a property than it is from a
variable?
Once we start down this road, we should consider a directive for
variable declarations to be used by the class rather than the instance,
perhaps something like:
scriptObject local MyVar
..or:
local to scriptObject myVar
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
Follow me on Twitter: http://twitter.com/FourthWorldSys
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
