On Apr 13, 2008, at 1:35 , Xavier Noria wrote:
> M::CONSTANT_TO_AUTOLOAD
>
> The second use case is less flexible than the first one because
> there's no doubt that if there's any CONSTANT_TO_AUTOLOAD to look
> for it should be defined in some m/constant_to_autoload.rb. It
> should be a constant named "CONSTANT_TO_AUTOLOAD" that would belong
> to some module with at least basename "M".
Just for the archives: I forgot a "conventionally" there or something
like that. Technically the basename of the class or module under the M
in M::CONSTANT_TO_AUTOLOAD may not be "M". For example this way:
module X; end
M = X
M::CONSTANT_TO_AUTOLOAD
There the (base)name of the module under M is "X".
-- fxn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
