I dislike the double leading underscores, personally. Re namespace collisions: since you have built in inserting a handler into a specified object's script, perhaps you could just check that there is no handler in that script with the same name before allowing the insert, and if there is, give the user a chance to change the name of the handler.
-- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Mar 7, 2015, at 8:37 AM, Michael Doub wrote: > I originally did this because I thought it would avoid name space collisions. > I thought that I would receive feedback if folks thought it was a bad idea. > As you can see, it is extra work and it is easy for me to make a mistake. > > I would be happy to remove them if folks would find it more useful. Please > just let me know. > > -= Mike > > > > > On 3/7/15 1:35 AM, Richard Gaskin wrote: >> Mark Wieder wrote: >> > If you're going to prefix the functions with "__" then you need to do >> > it everywhere. >> >> I think I missed something - why the underscores? >> >> I've seen a fairly common convention of using a single underscore for >> private settings and such, but never two. >> >> What value is being added to the library user with "__"? >> > > > _______________________________________________ > 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
