From: Sean O'Dell <sean@...>
Date: 2004-05-29T02:53:27+09:00
Subject: Re: Calling global method

On Friday 28 May 2004 10:41, ts wrote:
> >>>>> "S" == Sean O'Dell <sean@celsoft.com> writes:
>
> S> There really should be a module called global, or perhaps an object
> named S> global, that keeps all the global variables and methods.  That way
> you could S> just call global.method.  There should also be syntax sugar to
> allow you to S> 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.

	Sean O'Dell