RE: weaktables x __gc [was Re: two problems with luaL_loadbuffer and error capture (are they bug s ?)]

[Benoit Germain <bgermain@...>]

In other words, since the value is garbage, the entry in the unicity table
has already been cleared in the first phase of the gc cycle, and it is
normal that the __gc metamethod gets nil when trying to retrieve it
(therefore it doen't even have to clear it). Oh well, I guess I'll just have
to change my code and consider this is not an error. It would be a good
thing if your explanation made it in the manual, so that I don't get caught
twice :-)


Thanks for your quick reply.