Your abuse of nil spawned this discussion. Sufficient mechanisms exist
to solve your problem so you'll have to forgive the push-back from
more conservative users of the language. Myopic feature cramming in
languages is what gave us Python. This has been a long discussion and stuff can get mixed up. My original post suggested a new Lua value that I arbitrarily named 'empty' that was explicitly NOTHING to do with 'nil' and did not alter ANY table behavior or ANY of the properties of nil. 'empty' was simply an ordinary Lua value that (like any other) could be placed in any array. I'm not clear on how this "abuses" anything, and in particular nil.
--Tim
|
