Re: Problems with lposix on win32
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: Problems with lposix on win32
- From: Rici Lake <lua@...>
- Date: 2006年1月17日 13:14:13 -0500
On 17-Jan-06, at 11:54 AM, D Burgess wrote:
Ignoring the existing io package issues for a second, returning an
error
for most of the osex functions proposed is easy. But what object could
be used to hold the error for the files() iterator? Any syggestions?
nil, errorstring - error
nil,nil - ok termination
That doesn't work; it has to be false, errorstring.
In Lua's iterator protocol, the nil will terminate the for loop and the
errorstring will never be seen. Hence my comment that it has to be
<false, errorstring>, and the consequence that it has to be dealt with
explicitly in every for loop with that architecture.
- References:
- Problems with lposix on win32, Chris Marrin
- Re: Problems with lposix on win32, D Burgess
- Re: Problems with lposix on win32, Chris Marrin
- Re: Problems with lposix on win32, D Burgess
- Re: Problems with lposix on win32, Edgar Toernig
- Re: Problems with lposix on win32, Chris Marrin
- Re: Problems with lposix on win32, Rici Lake
- Re: Problems with lposix on win32, Chris Marrin
- Re: Problems with lposix on win32, Rici Lake
- Re: Problems with lposix on win32, Chris Marrin
- Re: Problems with lposix on win32, D Burgess