RDoc produces HTML and command-line documentation for Ruby projects. RDoc
includes the +rdoc+ and +ri+ tools for generating and displaying online
documentation.
See RDoc for a description of RDoc's markup and basic use.
Changes:
=== 3.6 / 2011-05-13
* Major Enhancements
* Interactive ri is now the default when no names are given.
* Minor Enhancements
* RDoc::RDoc#generate was added to allow multiple generators to be used with
a set of parsed file info.
* RDoc::Options#finish can be called multiple times now.
* `ri -i` only shows one level of namespace when completing class names.
* Added `ri --list` for explicit listing. `ri -l F G` will list all classes
or modules starting with F or G
* Bug fixes
* Remove windows-specific test for test_check_files, it is too hard to do.
Ruby commit r30811 by Usaku Nakamura.
* Remove unnecessary (and wrong) platform-dependent hacks. Ruby commit
r30829 by Usaku Nakamura.
* Completing via Array#[ in `ri -i` no longer crashes. Ruby Bug #3167
* Completing IO::o in `ri -i` now returns results. Ruby Bug #3167
* RDoc::Parser::C ignores prototypes better. Pull Request #34 by Pete
Higgins.
* private_class_method and public_class_method are now parsed correctly for
inherited methods. Issue #16 by gitsucks.
* The doc directive now forces documentation even when the method is marked
private or protected.
I wonder how I can get ri not to say
"Gem::Specification#default_executable= is deprecated with no
replacement" about a zillion times at the start of every call...?
Maybe it works without the --no-extension switch for you, but that can
break some gems as far as I can see.
Vale,
Marvin
···
Am 16.05.2011 19:29, schrieb Matt Neuburg:
Eric Hodel <drbrain@segment7.net> wrote:
rdoc version 3.6 has been released!
Looking good.
I wonder how I can get ri not to say
"Gem::Specification#default_executable= is deprecated with no
replacement" about a zillion times at the start of every call...?
Am 16.05.2011 19:29, schrieb Matt Neuburg:
> Eric Hodel <drbrain@segment7.net> wrote:
>
>> rdoc version 3.6 has been released!
>
> Looking good.
>
> I wonder how I can get ri not to say
> "Gem::Specification#default_executable= is deprecated with no
> replacement" about a zillion times at the start of every call...?