[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: How shall a Lua file handle be known?
- From: Reuben Thomas <rrt@...>
- Date: Wed, 11 May 2011 23:16:15 +0100
On 11 May 2011 23:07, Mike Pall <firstname.lastname@example.org> wrote:
> I'd rather add io.fdopen() and fp:fileno(), because these are
> useful for the FFI, too. Ok, so you'll need to fetch io.fdopen
> once at the start and put it into an upvalue. Not sure if you're
> happy with that.
I'd be delighted, but for a library I would prefer it be standard [and
I will remove pipe, fdopen and dup from luaposix until there's a
proper way to implement them. Is there any need for LuaJIT to
implement fileno? The current luaposix implementation is:
static int Pfileno(lua_State *L) /** fileno(filehandle) */
FILE *f = *(FILE**) luaL_checkudata(L, 1, LUA_FILEHANDLE);
return pushresult(L, fileno(f), NULL);
which works fine in LuaJIT 2.0.0-beta7:
LuaJIT 2.0.0-beta7 -- Copyright (C) 2005-2011 Mike Pall. http://luajit.org/
JIT: ON CMOV SSE2 SSE3 fold cse dce fwd dse narrow loop abc fuse
> require "posix"
> print (posix.fileno(io.stderr))