[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: io:lines() and \0
- From: steve donovan <steve.j.donovan@...>
- Date: Fri, 21 Feb 2014 09:44:45 +0200
On Fri, Feb 21, 2014 at 9:35 AM, René Rebe <rene@exactcode.de> wrote:
> Why is it you insists so much to refuse to improve a Lua core function to
> return more precisely what the underlying system actually returned?
Because, when will it stop? We all now that bad implementations and
ambiguities have created broken C run times. Should Lua compensate
for all of them?
(There are exceptions which make sense: e.g. Windows' strftime is so
broken that it will crash when passed formatting options it does not
understand, so 5.2 checks the input)
- References:
- io:lines() and \0, René Rebe
- Re: io:lines() and \0, steve donovan
- Re: io:lines() and \0, René Rebe
- Re: io:lines() and \0, Enrico Colombini
- Re: io:lines() and \0, steve donovan
- Re: io:lines() and \0, René Rebe
- Re: io:lines() and \0, Sean Conner
- Re: io:lines() and \0, Roberto Ierusalimschy
- Re: io:lines() and \0, René Rebe
- Re: io:lines() and \0, Cezary H. Noweta
- Re: io:lines() and \0, René Rebe
- Re: io:lines() and \0, Dirk Laurie
- Re: io:lines() and \0, René Rebe
- Re: io:lines() and \0, Craig Barnes
- Re: io:lines() and \0, René Rebe