[Matt answered my off-list message directly, so I'll put it up. -- Scott] Hey Scott, If I understand correctly you are interested in understanding the Rails internals and how Ruby processes the code, is that correct?
More precisely you are interested in knowing more about the load path, Rubygems and load/dependency order & management. I actually didn't think about that topic but it's a good one and a lot of people get bitten by this. As a matter of fact, Patrick found a load order bug recently with one the plugin he uses. Are others interested? The Ruby internal presentation is more about the C code, how it works, what are the APIs and the big parts of the code. It's obviously much more low level. - Matt On Dec 2, 2010, at 7:24, Scott Olmsted <[email protected]> wrote: > Matt, > > Indeed, we hope to see more of you at SDRuby, you're missed! > > I'm not posting this because it seems rather trivial, but I would like > to know how a Ruby app, and Rails in particular knows where all the > code it uses is located. Is there an internal "path"? Does Rails add > paths to gems to this path? Or am I completely off-base, does an app > "assimilate" (make its own internal representation of) all Ruby code > when it encounters it (such as Rails going out for gem code, or for > any of a Rails app code, for that matter) and so never need to go > there again? > > I think that's +1 for Ruby Internals. > > Thanks, > > Scott On Dec 1, 11:52 pm, Matt Aimonetti <[email protected]> wrote: > I promised Patrick that in 2011 I will find more free time to make it to the ..... -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
