Scripts will only be broken if they rely on the existence of the table member "n", rather than going through getn/setn. If this is a problem then you will probably want to override table.getn and table.setn to ensure consistency with the old implementation. -----Original Message----- From: lua-bounces@bazar2.conectiva.com.br [mailto:lua-bounces@bazar2.conectiva.com.br]On Behalf Of Bilyk, Alex Sent: Monday, May 24, 2004 12:12 PM To: Lua list Subject: RE: Change in behaviour of "n" field in Lua 5.1(work) I am with you on the t.n part. My scripts also rely heavily on table.insert/remove updating the size. So, 90% of my scripts will be broken with the next release. I guess others with the same problem would have to reimplement remove/release unless they are taken care of by the standard distro. Alex.
<<attachment: winmail.dat>>