Thanks all, interesting discussion There is another aspect of function/handler naming which is their names in relation to APIs - for example I might have a checkConnectivity() function in an mainstack's stack or card which calls a cgi.checkConnectivity() function in a code library called “cgi” - prepending each handler and function in the code library with “cgi” helps me keep track of what is going on and (I think) makes it easier to maintain and use across different mainstacks…
…just my two penneth… Dave > Thanks for taking the time to write such a considered response Mark > > > > Are these names any better than the ones already used in the library? It is > > hard to say - naming preferences are highly subjective! > > > I like them, the only thing I’m not sure about is the multiple `mime` in > each. > > > Just my two pence. > > Worth much more that the current face value! > > 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
