[#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: [MemLeak] in dln.c

From: matz@... (Yukihiro Matsumoto)
Date: 2002-09-03 00:56:30 UTC
List: ruby-core #406
Hi,

In message "Re: [MemLeak] in dln.c"
    on 02/09/03, Michal Rokos <m.rokos@sh.cvut.cz> writes:

|On Tue, Sep 03, 2002 at 12:00:42AM +0900, Yukihiro Matsumoto wrote:
|> I'd use alloca.  I want dln.c to be separatable from Ruby as much as
|> possible.
|
|	So, #2 is a winner.
|
|	(Only think that worries me is 'man alloca': The alloca function
|	is machine and compiler dependent. Its use is discouraged.)
|
|	All credits goes to nobu.

It seems OK (for me).  If you check if it works, go ahead to commit.

							matz.

In This Thread