From: gsm.beamon@...
Date: 2006-10-19T08:45:07+09:00
Subject: Re: Why Class decls and API docs don't Match

> b) Your problem/question seems not to be the fact that the rails
> documentation, or the tool that rails uses to generate its
> documentation, does not include information you want to see, right?
Yes. But not on purpose. The the thrust of my question was:
If this code is unambigous:

class ApplicationController < ActionController::Base
    layout "standard"
end

Then how come layout can't be found can't be found in
ActionController::Base?
For in all C++/java/Eiffel languages layout() would be a method in
ActionController::Base
or its superclasses. Period.

Now I understand that rdoc comes with a story as to why it doesn't
include layout.
And, really, that's fine.

But it still leaves open the question: what method would show that? For
on a complex library like Rails programmers can't be spending their
time trying to figure out what objects can call or manually inspecting
obj.inspect or whatever ....

> This is a tricky nut to crack. ActionController::Layout is included in
> ActionController::Base in action_controller.rb like this:
Yes, I belatedly found that the right thing to do and would have
largely answered my question.
See my other post.