[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: [ ruby-Patches-7499 ] RDoc patch that fixes rb_const_define output

From: "Daniel Berger" <djberg96@...>
Date: 2006-12-31 03:16:54 UTC
List: ruby-core #9810
On 12/30/06, Eric Hodel <drbrain@segment7.net> wrote:

<snip>

> Does the input end up being:
>
> /* value: 300 The perfect score in bowling */
> rb_define_const(...);
>
> ?
>
> Can the value derictive be ":value: 300" to match the rest of the
> RDoc directives?

No, I didn't mean to imply that I was using "value" as a literal tag.
The input line would just be:

/* 300: The perfect score in bowling */

Take a look at the file I attached (on RubyForge) - that has a pretty
good selection of examples I think.

It doesn't have to be that exact syntax, obviously, but I thought that
was pretty straightforward.  I'd rather not do literal tags for what
will likely just be one line comments in the majority of cases.

On a side note, I've noticed that multiline comments for constants
don't format properly (with or without my patch) - they seem to indent
on the newline.  But, I'll worry about that in another patch. :)

Regards,

Dan

In This Thread