[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: [ANN] Lua 5.2.0 (alpha) now available
- From: Luiz Henrique de Figueiredo <lhf@...>
- Date: Tue, 16 Nov 2010 18:41:25 -0200
> this quick switch from work5 to alpha was quite a surprise (for me - my bad
http://lua-users.org/lists/lua-l/2010-10/msg00834.html said that we were
getting close to an alpha version. Note that we're still at alpha-rc1.
> I noticed that Lua's build is quite customizable through luaconf.h, so I
> wonder how a script can detect the different options used to compile the
> Lua interpreter under it is running.
Try this:
gcc -E -P - -I. <<EOF
#include "lua.h"
VALUE_OF_LUAL_BUFFERSIZE = LUAL_BUFFERSIZE
EOF
But I understand that this is not from inside running a Lua interpreter.
> Couldn't some of those defines (or even some other parameters not found
> in luaconf.h, like max number of item that can be unpacked) be made
> available as "constants" in a table, or maybe through a function
You can do that yourself, using the technique above.
> Am I missing something why Lua doesn't provide such informations? Isn't
> that so useful as I think?
It's probably not that useful. Plus it encourages complicated programming.