[#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: Patch to add a Module#const_missing method

From: JanArne.Petersen@... (Jan Arne Petersen)
Date: 2002-09-06 12:49:54 UTC
List: ruby-core #448
Hi,

Am Fre, 2002-09-06 um 13.17 schrieb nobu.nokada@softhome.net:
> Hi,
> 
> At Fri, 6 Sep 2002 10:23:50 +0900,
> Yukihiro Matsumoto wrote:
> > |I wrote a patch to add a Module#const_missing method like the 
> > |Object#method_missing method to Ruby.
> > 
> > Thank you for the patch.  But we have to discuss whether we need this
> > hook.  Hook is sometimes useful but since we can not add every
> > possible hook, we have to draw line somewhere.  Opinion, everyone?
> 
> Already we have autoload, and it can be considered a special
> form of const_missing, I guess.

The problem with autload is that you have to register the name of the
constants first and you cannot call a proc on request but only 'require'
a specific file.

In contrast 'const_missing' can be used to create classes on demand if
you don't know the name before it is requested and you can execute any
code in the 'const_missing' method.


Jan Arne Petersen

In This Thread