This is all great fuel for the scripting style panel at the conference. Also we have:
- strict compilation - being even stricter by also declaring repeat loop iteration variables (I do this) - declaring variables at the top of the handler or in the block they are used. Ali and I do the latter and Peter B thinks it's poor style because we don't have block scoped variables. - anything else we can come up with Cheers Monte Sent from my iPhone > On 9 Jul 2016, at 5:00 AM, Mark Wieder <mwie...@ahsoftware.net> wrote: > > Richard Gaskin <ambassador@...> writes: > >> >> J. Landman Gay wrote: >> >>> Since behavior scripts are only referenced in a "set the behavior" >>> statement, I'm not sure where you'd use an initial flag. >> >> Not in code, just in the object name. > > I use the word "behavior" in the object name, as in > > button "btnStorageFieldBehavior" > or > stack "PageObjectsBehavior" > >> >>> But if I ever need one, I'd use "b" for "behavior". >> >> I could, but I'm still holding out hope that the original term LC first >> implemented this with, parentScript, will one day become the preferred >> token for that. > > I think "parent" has the possibility of becoming confused with "owner" > when thinking of the message path, so I like "behavior" a bit better. > I'd probably prefer "shadow", as I think of behavior/parent scripts as > private backscripts for objects. > > -- > Mark Wieder > ahsoftw...@gmail.com > > > > > _______________________________________________ > 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 _______________________________________________ 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
