Rdoc 3.6 Released

rdoc version 3.6 has been released!

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.

Eric H. [email protected] 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…?

Thx - m.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 16.05.2011 19:29, schrieb Matt N.:

Eric H. [email protected] 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…?

Read the RubyGems 1.8 announcement.

gem pristine --all --no-extensions

Maybe it works without the --no-extension switch for you, but that can
break some gems as far as I can see.

Vale,
Marvin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN0YedAAoJELh1XLHFkqhaa00H/1yLWrV7Q6zwzBAgXwe0q1Is
wIFDttQ05gca55pgYH6ZwG0alX5xS/vLgsVTXGuHG1XdBZ3yo58dByV/TSFNsJSF
UrWdZQMT9tZhS3EblPXZaqms/BakVyawwxqN5Gp7QAki3Pjny1rk+jDASZA45Xp2
WLdCLI7Zhku31CZeeVU0F2baYc7Y3ONkwAElJYDmq+OrRvwde6HAtcdzz5OFvMco
t6i0AgjB08IKaXtylhCV7EwySyjpPEB1VkgRjFcyIgP2bhayxjGgkG89vWjzi1N8
3KRXGXftCTSEg9BQP9Xrv4nk7awwHtAvLJjT7ZMIibEZc0dO1O2PdKqpJbV2YRM=
=DJ0Q
-----END PGP SIGNATURE-----

On May 16, 2011, at 17:59 , lists wrote:

Nothing known about Array
$

If you’re on 1.8, you’ll need to install rdoc-data and follow the
post-install instructions.
If not, I dunno with this little info.

W dniu 11-05-17 02:59, lists pisze:

On May 13, 2011, at 7:30 PM, Eric H. wrote:

rdoc version 3.6 has been released!

Surely I’m missing something simple. After upgrading, I now get:

$ ri Array
Nothing known about Array
$
If you’re using RVM I belive that running rvm docs generate (or
generate-ri or generate-rdoc) will fix it.

On May 13, 2011, at 7:30 PM, Eric H. wrote:

rdoc version 3.6 has been released!

Surely I’m missing something simple. After upgrading, I now get:

$ ri Array
Nothing known about Array
$

On May 16, 2011, at 10:25 PM, Ryan D. wrote:

Surely I’m missing something simple. After upgrading, I now get:

$ ri Array
Nothing known about Array
$

If you’re on 1.8, you’ll need to install rdoc-data and follow the post-install
instructions.
If not, I dunno with this little info.

That was it, thank you! I did actually try searching
http://rdoc.rubyforge.org/ first, but didn’t find anything about
rdoc-data and ruby 1.8.

Quintus [email protected] wrote:

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…?

Read the RubyGems 1.8 announcement.

gem pristine --all --no-extensions

I did that and it didn’t help. m.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs