[#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:33981] Re: Multi-line comments

From: Loren Segal <lsegal@...>
Date: 2010-12-28 22:54:48 UTC
List: ruby-core #33981

On 12/28/2010 5:37 PM, Ryan Davis wrote:
> On Dec 28, 2010, at 13:16 , Loren Segal wrote:
>
>> I believe RDoc has (or used to have) special code for docstrings beginning with "##". [...]  I actually *don't* understand why this is necessary
> The only place this is required in my code is in front of non-methods like attr*s or define_methods. Otherwise I have no idea why you're positing that the "##" is "necessary" as it obviously isn't.

I never said it was necessary in RDoc, I was questioning why it was 
necessary in general.

>> and you can "opt out" by inserting extra whitespace after a comment block in Ruby
> huh? you can?
>
In YARD, yes. I would consider the behaviour to be unreasonable if a 
tool generated documentation for the following gist with so much 
whitespace: https://gist.github.com/757859

I hadn't actually tested this in RDoc until now. I figured it did the 
sane thing and stopped following a comment after enough whitespace. I 
was actually surprised to find out that it does not, so I guess you 
can't in RDoc, but you can in YARD.

YARD actually waits for 2 lines of whitespace to stop following a 
comment, so your code still actually documents fine in both tools. Any 
more empty lines and it would not, though.

- Loren

In This Thread