From: Yukihiro Matsumoto Date: 2005-03-08T11:58:50+09:00 Subject: 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:41:45 +0900, Daniel Berger writes: |> class Errno::NOERROR |> end |How about Errno::UNKNOWNERROR? Or Errno::UNDEFERROR? |Errno::NOERROR seems like a contradiction. Errno::NOERROR (or whatever) is an system call exception class that would never be raised from any system call. An exception class which is not supposed to be raised is something contradicting by nature. I think your feeling reflects this situation. It's not UNKNOWNERROR since it's known. UNDEFERROR sounds strange for me, since it's explicitly defined (in a sense). I am open to other name proposals. matz.