On 25 April 2012 11:11, Sergey Ezhov <[email protected]> wrote:
> Try, for example, to find a method "method_missing". Fail!

http://rubydoc.info/stdlib/core/1.9.3/BasicObject#method_missing-instance_method

example fail...

> How I can trust documentation in which methods about which I already
> know aren't described?

A null hypothesis.

>> And the very handy Rails API docs:
>>   http://api.rubyonrails.org/
> Bad documentation! There are no descriptions of many classes, there are
> no descriptions of many methods, there are no descriptions of parameters
> of methods, there are no descriptions of ALL possible parameter values
> of methods.

*sigh* so write them... or ask about specific places where you're stuck.


Look, you're talking about things being difficult for beginners, and
then wave "method_missing" as an example - to play with that is pretty
serious meta-programming which will blow up horribly if you don't know
what you're doing. There *is* plenty of reference for *how* to use
method_missing if you look for it, even if it is not mentioned in the
core docs.

If you expect *everything* to be totally complete before you start
using it, then you're going to be disappointed (in life, not just in
Ruby/Rails). In all seriousness, if a few holes in documentation
frustrate someone so much that they "stop and leave from Ruby and
Rails" then maybe it wasn't for them in the first place - it takes all
sorts to run the world, and everything is not for everyone :-/

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" 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-talk?hl=en.

Reply via email to