Yep, I'm doing just about all those things. What I didn't do is use a naming convention that indicates where in the message path the called handler is. So if I call dbDoit from a control, where does dbDoit reside? In the control script, on the card/stack that the control is in, on the mainstack for the app, in some library totally outside the main stack that's been inserted as a front/back script, stuff like that.
Pete Molly's Revenge <http://www.mollysrevenge.com> On Wed, Apr 20, 2011 at 11:05 AM, Bob Sneidar <b...@twft.com> wrote: > Oh heck yeah, especially if you use a scripting utility that allows you to > sort handlers. For instance, all my commands and functions for opening, > closing, and idling databases start with db. All my functions that take > parameters and return a value start with get. The big thing is to use names > that are descriptive. They may be harder to type, but readability in a large > app becomes paramount, especially if you have a memory like mine that > flushes all unused information over a month old. > > Bob > > > On Apr 20, 2011, at 9:15 AM, Pete wrote: > > > I agree, learned how to avoid several gotchas! > > > > The book has a section on naming conventions for variables and that's > been > > discussed several time on the list, but does anyone use naming > conventions > > for their commands/functions? > > > _______________________________________________ > 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
