[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: How shall a Lua file handle be known?
- From: Michael Truog <mjtruog@...>
- Date: Sun, 13 May 2012 00:40:17 -0700
Has anything changed where it is now possible to create
io.fdopen() or something similar in a separate library?
If so, is there now a library that has an implementation?
(it still seems like luaposix does not have fdopen())
On 05/11/2011 23:16, Reuben Thomas <firstname.lastname@example.org> wrote:
> On 11 May 2011 23:07, Mike Pall <email@example.com> 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
> documented!]. Team?
> 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))