From: Austin Ziegler <Austin.Ziegler@...>
Date: 2004-05-29T03:56:39+09:00
Subject: Re: Calling global method

>>S> There really should be a module called global, or 
>>S> perhaps an object named global, that keeps all the global
>>S> variables and methods. That way you could just call
>>S> global.method. There should also be syntax sugar to allow you
>>S> to say ::method.
>> "global" methods are private : this is why you can't call
>> Object.test
>> 
>> svg% ruby -e 'def test() end; p Object.test'
>> -e:1: private method `test' called for Object:Class (NoMethodError)
>> svg%
> Yes, but that's not how globals usually behave. Globals are
> usually always globally available unless overridden or removed.

Does Ruby *need* globals, especially given that Kernel already
exists?

-austin
--
austin ziegler * austin.ziegler@evault.com