Somewhere I once ran across a list of suggested lc naming conventions, it helped me greatly. If I recall it was s for script locals, t for handler locals (t for temporary) g for globals, k for constants, c for custom properties. and I don't know if it was in the same list, but I add a trailing A for arrays. Sure makes it easy to keep track of whats what, so to whoever wrote that list.. Thank you!
On Thu, Jul 7, 2016 at 6:00 PM, Alex Tweedly <a...@tweedly.net> wrote: > What do you use for handler-local variables ? > > Thanks > > Alex > > > On 07/07/2016 23:16, Monte Goulding wrote: > >> On 8 Jul 2016, at 7:52 AM, Scott Rossi <sc...@tactilemedia.com> wrote: >>> >>> I've always thought lowercase "L" is a poor choice to prefix a variable >>> name. Is it an L? It is a capital i? Is it a pipe? >>> >> For what it’s worth we use `s` in the team for script locals. There are >> some older scripts like libURL that use some other prefixing conventions. >> >> Cheers >> >> Monte >> _______________________________________________ >> 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 > _______________________________________________ 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
