Re: Problems with lposix on win32

[Rici Lake <lua@...>]

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.