> JLG wrote: > ... "t" for handler-local variables, "g" for globals, > "s" for script-locals, and "k" for constants ... > If you adopt a system like this, you'll never have a > naming conflict.
> Mark W. wrote: > tExt is all I'll say ;) (thanks to Ken Ray for that one) The LC Builder StyleGuide recommends "m" for widget static variables. There is indeed a useful thing one can do with that, so that a lot of things sound familiar to me(!). private variable mE as ScriptObject put my script object into mE Now this is valid and unambiguous code both in LCB and LCS send "mouseDown" to mE ;-) _______________________________________________ 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
