www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2013/07/20/06:50:15

X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Message-ID: <51EA6B9C.5010307@gmx.de>
Date: Sat, 20 Jul 2013 12:51:08 +0200
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121025 Thunderbird/16.0.2
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Set _IOERR if the file stream has been opened in wrong mode.
References: <51E5D0C6 DOT 1060404 AT gmx DOT de> <83y5951a79 DOT fsf AT gnu DOT org> <51E702E0 DOT 3010809 AT gmx DOT de> <83fvvc1t0x DOT fsf AT gnu DOT org> <8738rcsdik DOT fsf AT uwakimon DOT sk DOT tsukuba DOT ac DOT jp> <201307180459 DOT r6I4xWxV010383 AT envy DOT delorie DOT com> <51E9D758 DOT 8000209 AT gmx DOT de> <CAA-ihx_SR7sb9+Tq_Ok+VM9FbjPLp9Lvk8a+bXf94oj13MTeWg AT mail DOT gmail DOT com>
In-Reply-To: <CAA-ihx_SR7sb9+Tq_Ok+VM9FbjPLp9Lvk8a+bXf94oj13MTeWg@mail.gmail.com>
X-Provags-ID: V03:K0:YRsxht8vucX/szynGGTDcsCqBZhPP3VeUn8g7xVeIRwvTo/omIi
0mz091Wh3tVAVPhUeI8hfv7SDVwAwzeQqWAK3wqXAmI0AvPFyRS29/X3Xns3gzNi84wH50W
kn80orgcARtLlF3SPvwFgQ4jiMf76bD3BoVSMYpicXBI1t4sTlQvgy3FbH6ITD/DTEQKD+N
Q29iv+WUSr6YT/RVJs7Bw==
Reply-To: djgpp-workers AT delorie DOT com

Am 20.07.2013 03:26, schrieb Rugxulo:
> Hi,
>
> On Fri, Jul 19, 2013 at 7:18 PM, Juan Manuel Guerrero
> <juan DOT guerrero AT gmx DOT de> wrote:
>> Am 18.07.2013 06:59, schrieb DJ Delorie:
>>
>> If I get no positive response or any response at all, I will not insiste in
>> this issue anymore and assume that it is prefered to keep the current
>> behavior of the library.
> (It's not really my decision, so this is just an opinion.) Sure, fine,
> go ahead and patch it. But I still think it's sloppy on their end
> (Lua, et al.) to use such a broken idiom. But there's no reason to be
> too stubborn if actual code relies on it.
>
> P.S. I'm not subscribed to the Lua mailing list, but apparently that's
> the preferred way to report bugs, etc. If you'd like, I'll go ahead
> and subscribe and then forward your findings and report back any
> relevant comments.


Feel free to go ahead reporting this issue.  I have no objections, I may
follow the discussion started by you in that mailing list but I will neither
subscribe to that list nor participate in the discussion.  If you want to
contact me you can use this one or comp.os.msdos.djgpp.

This time, to check the lua port I have decided to use their test suite
available as: http://www.lua.org/tests/5.2/lua-5.2.2-tests.tar.gz.
As you may know they claim:

"The tests will print lots of different messages, but no assertion should ever fail.
  If the test goes all its way to the end, printing a "final OK" message, then all went well.

  Note that, by its very nature, Lua is heavily dependent on the underlying standard C libraries.
  Sometimes the test suite fails because these underlying C libraries do not follow the ANSI standard.
  There is not much we can do about it."

This way I discovered two issues.  The first was the rounding bug for hex
string conversion in strto[d|f|ld] and the second one and much more
difficult to debug was this one.  With these fixes the (small) test suite
passes.  The big test suite fails with djgpp and with linux.  Here a lot
of posix and/or ansi support is missing and I will certainly not try to
implement it.

It would be interesting to know how they know that it can be taken for
granted that a stream error condition will be triggered and the error indicator
will be set by code like the sample code I posted.


Regards,
Juan M. Guerrero

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019