[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: [ANN] Lua 5.4.0 (work1) now available
- From: Coda Highland <chighland@...>
- Date: Wed, 14 Mar 2018 11:29:38 -0500
On Wed, Mar 14, 2018 at 11:00 AM, Rena <hyperhacker@gmail.com> wrote:
> On Wed, Mar 14, 2018, 10:27 Roberto Ierusalimschy, <roberto@inf.puc-rio.br>
> wrote:
>>
>> > In the presence of holes, #t seems to still have the same
>> > easy-to-define/hard-to-understand semantics from Lua 5.1-5.3.
>>
>> I said this in my first post:
>>
>> You still can create tables with holes, but you must get out of your
>> way to do it.
>>
>> Once you get out of your way and create holes, all the "standard
>> behavior" are back. But you asked for it...
>>
>> -- Roberto
>
>
> Well, it seems like now that tables can contain nil, it makes little sense
> that sequences can't.
You misunderstand.
The example given had a sequence that contained nil. It was only when
the table key was explicitly removed with undef that a hole was
introduced.
/s/ Adam
- References:
- Re: [ANN] Lua 5.4.0 (work1) now available, Coda Highland
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Coda Highland
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Russell Haley
- Re: [ANN] Lua 5.4.0 (work1) now available, Coda Highland
- Re: [ANN] Lua 5.4.0 (work1) now available, Hisham
- Re: [ANN] Lua 5.4.0 (work1) now available, Roberto Ierusalimschy
- Re: [ANN] Lua 5.4.0 (work1) now available, Rena