[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Unexpected table.remove behaviour.
- From: Enrico Colombini <erix@...>
- Date: Wed, 24 Jun 2009 22:49:36 +0200
Suppose you have a LONG table full of several thousand NMEA
> sentences or whatever.. If you need to thin data in place
> according to some rule, you need table.remove().
> But if you use ipairs() you work forwards from index 1.
I'm not sure I'd use a simple flat table in a case like this. Maybe a
linked list or some other structure could be more appropriate, depending
on the frequency of operations and their relative cost.