From: Joel VanderWerf <vjoel@...>
Date: 2003-12-08T14:47:38+09:00
Subject: subclassing Errno::XXX


What changed from 1.7.3 to 1.8.0 and 1.8.1 that could have caused this?

[~] ruby-1.7.3 -v -e 'class  MissingFileError < Errno::ENOENT; end; 
raise MissingFileError, "foo"'
ruby 1.7.3 (2002-12-20) [i686-linux]
-e:1: foo (MissingFileError)

[~] ruby-1.8.0 -v -e 'class  MissingFileError < Errno::ENOENT; end; 
raise MissingFileError, "foo"'
ruby 1.8.0 (2003-08-04) [i686-linux]
-e:1:in `initialize': uninitialized constant MissingFileError::Errno 
(NameError)
         from -e:1:in `exception'
         from -e:1:in `raise'
         from -e:1

[~] ruby-1.8.1 -v -e 'class  MissingFileError < Errno::ENOENT; end; 
raise MissingFileError, "foo"'
ruby 1.8.1 (2003-10-31) [i686-linux]
-e:1:in `initialize': uninitialized constant MissingFileError::Errno 
(NameError)
         from -e:1:in `exception'
         from -e:1:in `raise'
         from -e:1

I've decided to no longer subclass in this way, for other reasons, but 
I'm still curious. Is it a scope thing? Or just something about Errno?