Daniel Berger wrote:
...
> My main reason for wanting this behavior is that, in some cases, I
> declare constant values that aren't meant for public use.
> 
> A good example is the windows-pr stuff, where I'm converting C macros
> to Ruby values, or using constants to store function pointers from
> Win32API.  If you were to do 'require "win32/file"', and then print the
> results of File.constants, you would see dozens of constants, e.g
> File::INVALID_HANDLE_VALUE, File::DeviceIoControl, etc.  Most of those
> are not meant for public use and should not be visible directly by the
> end user.

What about putting them in a nested module?

-- 
        vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407