That works, but I prefer cleaner and user friendly code.
Mine would be obvious to whoever uses it that "here's how you edit it".
"Clean" and "user friendly" is all relative. I personally find Short Circuit's version better, but I wouldn't bother to quibble over it unless we were specifically discussing it.
We have had many complaints/threats/suggestions for our projects and our code style over the years, but there was one that stuck with me more than any other. We have two tables for whitelisting stool's prop movement and deletion, called "ULib.delWhiteList" and "ULib.moveWhiteList". If you look at them, this comment is by these tables:
-- Are you a STOOL author who's angry that your tool isn't on this list?
-- Just add this to your code:
-- if ULib then table.insert( ULib.delWhiteList, "my_stool" ) end
Well, a few years back, we had someone at Facepunch discuss how terribly coded our projects were, and pointed at these two tables. The user said that if we were good programmers, we would have coded an API to manipulate these tables (add, remove, check for values). I was shocked, and continue to be shocked. What's the problem with calling table.insert? When working in someone else's code, I'd rather stick with the tools Lua already gives me (as long as it makes sense), than work with their custom API.
Anyways, this story just goes to show you that everyone approaches problems differently and there's no "best solution".
