From: Michael Granger <ged@...>
Date: 2003-05-29T22:36:21+09:00
Subject: Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c

Hi,

I would have been using it for years now if it worked the way the 
recent changes allow. I encounter problems with load-order because of 
mutual requires a lot, and an autoload that can load modules into a 
namespace other than the top-most is a blessing. When I was first 
learning Ruby I was surprised that it didn't work this way.

Please, for the love of Pete, don't deprecate it now that it works! =:)

On Thursday, May 29, 2003, at 07:01 America/Denver, Dave Thomas wrote:

> nobu.nokada@softhome.net wrote:
>> Hi,
>> At Thu, 29 May 2003 12:16:52 +0900,
>> Dave Thomas wrote:
>>>>    * eval.c (rb_mod_autoload, rb_mod_autoload_p): new method;
>>>>      Module#autoload, Module#autoload?.
>>>
>>> This is probably a silly question, but does autoload ever get used? 
>>> Or
>>> is it possibly a Perlism that we might think about deprecating?
>> Kernel is a Module, so still you can call autoload everywhere.
>
> Agreed: I was wondering though if it is a function that actually gets 
> used in the real world, or should we be deprecating autoload, and 
> eventually remove it from the language?

--
Michael Granger <ged@FaerieMUD.org>
Rubymage/Believer/Architect
The FaerieMUD Consortium