Re: Undefined Errno::EPROTO and the like raises NameError

Hi,

In message "Re: Undefined Errno::EPROTO and the like raises NameError"
    on Tue, 8 Mar 2005 10:03:16 +0900, Yukihiro Matsumoto <[e-mail]> writes:

||I just run into the problem, that certain System Call Errors aren't 
||defined depending on the platform. I tested on a platform, where 
||Errno::EPROTO is not defined. If I code something like
|
|Yeah, it's on my to-do list for a long time, but without any idea to
|solve.  Errno exceptions vary platform to platform, so that simple
|scripts like you did cause NameError, but I don't want to allow
|reference to undefined constants in the rescue clause, since relaxing
|constant reference here changes the meaning of expression, and makes
|semantics more complex.  Any idea?

I got an idea right after sending above mail.  Than you Florian for
the source of inspiration.  The following code will stop your problem.

  class Errno::NOERROR
  end

  def Errno.const_missing(name)
    Errno::NOERROR
  end

I will merge this to 1.9 and see how good it works.

							matz.