[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: tables
- From: Chris <coderight@...>
- Date: Sun, 5 Mar 2006 17:54:24 -0500
What I find interesting is that an explicitly set nil value is not considered a "hole" in the table.
According to the documentation that shouldn't be. A bug?
By the way, I find the documentation wording very confusing:
The length of a table
is defined to be any
is not nil
***may*** be zero.
For a regular array, with non-nil values from 1 to a given
its length is exactly that
the index of its last value.
If the array has "holes"
(that is, nil
values between other non-nil values),
***may*** be any of the indices that
directly precedes a nil
(that is, it ***may*** consider any such nil
value as the end of
It _might_ consider a nil the end? Well, does it or does it
not? And if it can change I think that needs to be made clear.