Rails core - Aug 2006 - Re: Dependency related issues

On Aug 21, 2006, at 6:01 PM, nseckar@gmail.com wrote:
> I''d like to get down to either i) fixing all the dependencies
issues
> with the new code or ii) giving up and reverting to the old. It would
> really help if those of you who have had troubles could file some
> tickets and assign them to me. If you like, add
''dependencies'' to
> keywords.

My biggest problem is that I often organize code into subdirectories,  
but don''t follow the Java convention of placing that code into  
modules named after the subdirectories. This seems to break the  
autoloading.


Dave

Dave Thomas wrote:
> My biggest problem is that I often organize code into subdirectories,
> but don''t follow the Java convention of placing that code into
> modules named after the subdirectories.
You may call this "Java conventions" but this has also been our
convention since we started loading from modules.

Without the naming conventions we have now, there''s no way for
dependencies to know which file to load for a given constant. Since
Rails is all about conventions, I feel pretty fine in demanding a
meaningful code layout.

If the conventions we''ve adopted chafe too much, then you''re
free to
hack together something that will fit better. Adding qualified constant
names to Dependencies.autoloaded_constants is not public API, but it''s
there if you want to use it.


--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---