[#444] io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...>

I am encountering a problem similar to the one mentioned here,

19 messages 2002/09/06
[#453] Re: io_write()/fwrite() and EINTR on Solaris — nobu.nokada@... 2002/09/08

Hi,

[#454] Re: io_write()/fwrite() and EINTR on Solaris — matz@... (Yukihiro Matsumoto) 2002/09/09

Hi

[#469] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/09

On Mon, Sep 09, 2002 at 03:55:13PM +0900, Yukihiro Matsumoto wrote:

[#479] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/10

On Tue, Sep 10, 2002 at 01:04:10AM +0900, Jos Backus wrote:

[#492] Re: io_write()/fwrite() and EINTR on Solaris — Jos Backus <jos@...> 2002/09/21

On Wed, Sep 11, 2002 at 02:23:33AM +0900, Jos Backus wrote:

Re: [-Wall+fix?] parse.y

From: nobu.nokada@...
Date: 2002-09-23 16:25:23 UTC
List: ruby-core #498
Hi,

At Mon, 23 Sep 2002 23:44:29 +0900,
Michal Rokos wrote:
> 	1st part: 'return head' doesn't need to be in every case:, can
> 	be in the end. (Fixes: parse.y:4423: warning: control reaches
> 	end of non-void function)

I commited almost same modification just now.

> 	2nd part: Is this real fix for: parse.y:4438: warning: `t' might
> 	be used uninitialized in this function

Sorry, the code was incomplete and wrong.  By the previous
commitment, block_append() got to omit unused literals, so
NODE_BLOCK no longer needs special treatment for literal
concatenation.

Thank you.

-- 
Nobu Nakada

In This Thread