Re: Surprising behavior of table.insert()

[Axel Kittenberger <axkibe@...>]

> In your case, I suppose returning nil instead of more nothing than nil
> will circumvent your problems.

In a second though, I take that back. Just dont do nil's and lists,
its all bad news.
If you want to make a no-operation case, make an additional if around
the table.insert.
If you want to express something like "nil" in the list, use something
else, like false, NaN or a custom table tag you call "local nothing =
{}"