Absolutely ;) But when a script develops its own command-line parser, then it will collect as many flags as can fit on a typical terminal screen (many GNU utilities don't follow this simple constraint, alas) It puts out warnings in a form that editors understand, so e.g. I bind lglob to F7 in SciTE instead of plain luac.
lglob is pushing luac analysis to the point where to go any further will lead to problems. I will quote my favourite Irish joke: A gentleman goes to Dublin and gets lost. He asks a pedestrian "Tell me my good man, how do I get to the National Museum?". And the man responds "Well, sir, I would not go from here if I was you"[1]
Very applicable to software projects! In particular, lglob will never make Petitle Abeile happy because it can't handle his _ENV magic ;) It does know about the _ENV={} module trick however, just can't handle multiple such scopes.
It is suprisingly tricky to handle this kind of aliasing
local T = table print(T.join{1,2})
and still get an error on using 'table.join'. The resulting code will not earn any elegance awards.
steve d.
[1] I'm half Irish so I can tell non-offensive Irish jokes
