4 ms·
It says something when Ruby's notoriously shonky documentation is the paragon in an example like this. The comparison with, say Python, is even more illuminatin
by regularfry 16y ago
It says something when Ruby's notoriously shonky documentation is the paragon in an example like this. The comparison with, say Python, is even more illuminating.
- rb2k_ 16y agoI might be wrong, but in the case of String, not really: http://docs.python.org/release/2.5.2/lib/string-methods.html http://docs.python.org/release/2.5.2/lib/string-methods.html
- regularfry 16y agoThere's also http://docs.python.org/tutorial/introduction.html#strings http://docs.python.org/tutorial/introduction.html#strings, http://docs.python.org/library/string.html http://docs.python.org/library/string.html and http://docs.python.org/library/stdtypes.html#sequence-types-str-unicode-list-tuple-bytearray-buffer-xrange http://docs.python.org/library/stdtypes.html#sequence-types-.... There's a fair bit of duplication in there, yes, but I think it's a pretty good coverage overall. There are some absolute doozies in the Ruby documentation, particularly around IO and the Socket hierarchy. String is relatively ok.