[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Unexpected table.remove behaviour.
- From: lostgallifreyan <lostgallifreyan@...>
- Date: Wed, 24 Jun 2009 20:12:06 +0100
Dolphin <email@example.com> wrote:
>I agree that it is a little strange but #Y simply returns a value such that
>Y[#Y+1]==nil is true, but it is not guaranteed to be the lowest positive number
>that satisfies that requirement.
Then its usefulness is questionable except where a contiguous array fills a table from index 1 upwards. As table.remove has useful behaviour when there is a nil value in the table interrupting an array, this abberation makes it especially important to have setn. If it is to stay deprecated, what is to replace it? Where useful behaviour is restricted by undefined behaviour, it makes sense that we should be allowed to influence the definition directly.
setn is dead.
VIVA SETN!! >:)