[#33640] [Ruby 1.9-Bug#4136][Open] Enumerable#reject should not inherit the receiver's instance variables — Hiro Asari <redmine@...>

Bug #4136: Enumerable#reject should not inherit the receiver's instance variables

10 messages 2010/12/08

[#33667] [Ruby 1.9-Bug#4149][Open] Documentation submission: syslog standard library — mathew murphy <redmine@...>

Bug #4149: Documentation submission: syslog standard library

11 messages 2010/12/10

[#33683] [feature:trunk] Enumerable#categorize — Tanaka Akira <akr@...>

Hi.

14 messages 2010/12/12
[#33684] Re: [feature:trunk] Enumerable#categorize — "Martin J. Dst" <duerst@...> 2010/12/12

[#33687] Towards a standardized AST for Ruby code — Magnus Holm <judofyr@...>

Hey folks,

23 messages 2010/12/12
[#33688] Re: Towards a standardized AST for Ruby code — Charles Oliver Nutter <headius@...> 2010/12/12

On Sun, Dec 12, 2010 at 9:55 AM, Magnus Holm <judofyr@gmail.com> wrote:

[#33689] Re: Towards a standardized AST for Ruby code — "Haase, Konstantin" <Konstantin.Haase@...> 2010/12/12

On Dec 12, 2010, at 17:46 , Charles Oliver Nutter wrote:

[#33763] [Ruby 1.9-Bug#4168][Open] WeakRef is unsafe to use in Ruby 1.9 — Brian Durand <redmine@...>

Bug #4168: WeakRef is unsafe to use in Ruby 1.9

43 messages 2010/12/17

[#33815] trunk warnflags build issue with curb 0.7.9? — Jon <jon.forums@...>

As this may turn out to be a 3rd party issue rather than a bug, I'd like some feedback.

11 messages 2010/12/22

[#33833] Ruby 1.9.2 is going to be released — "Yuki Sonoda (Yugui)" <yugui@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2010/12/23

[#33846] [Ruby 1.9-Feature#4197][Open] Improvement of the benchmark library — Benoit Daloze <redmine@...>

Feature #4197: Improvement of the benchmark library

15 messages 2010/12/23

[#33910] [Ruby 1.9-Feature#4211][Open] Converting the Ruby and C API documentation to YARD syntax — Loren Segal <redmine@...>

Feature #4211: Converting the Ruby and C API documentation to YARD syntax

10 messages 2010/12/26

[#33923] [Ruby 1.9-Bug#4214][Open] Fiddle::WINDOWS == false on Windows — Jon Forums <redmine@...>

Bug #4214: Fiddle::WINDOWS == false on Windows

15 messages 2010/12/27

[ruby-core:33976] Re: Multi-line comments

From: Eric Hodel <drbrain@...7.net>
Date: 2010-12-28 21:34:43 UTC
List: ruby-core #33976
On Dec 28, 2010, at 13:16, Loren Segal wrote:
> On 12/28/2010 7:12 AM, Rodrigo Rosenfeld Rosas wrote:
>> Regarding documentation, I like the format used by Doxygen and Javadocs, like using /** */ (or /*! */) and //!. I don't understand why the same idea was not followed in Ruby, like using '#!' and '/*! */' besides '=begin/end'.
> 
> IIRC this was attempted. I'm not positive, but I believe RDoc has (or used to have) special code for docstrings beginning with "##". That still is a convention used in some documentation, but it's only a stylistic convention. I actually *don't* understand why this is necessary, and honestly, I didn't understand why this was necessary in Java either. If a comment appears immediately before a documentable element, it's probably documentation anyway-- most comments are, in fact, "documentative". IMO it seems a little silly to introduce a new syntax to opt-in to documentation

In RDoc ## is only required when the comment does not come before a documentable element but you wish to indicate a method has been created.  For example, methods generated by metaprogramming.  See "Metaprogrammed Methods" and "Hidden methods and attributes" here:

http://rdoc.rubyforge.org/RDoc/Parser/Ruby.html

> -- we should be opting *out* of documentation (and you can "opt out" by inserting extra whitespace after a comment block in Ruby), because comments are more often than not going to be documentation.

RDoc assumes you are documenting everything except in cases where it can't know like metaprogramming.  To opt out of documentation use nodoc or stopdoc/startdoc.

In This Thread