[#3228] Core support for Gems, and namespace — "Luke A. Kanies" <luke@...>

Hi all,

21 messages 2004/07/27
[#3230] Re: Core support for Gems, and namespace — Austin Ziegler <halostatue@...> 2004/07/27

On Tue, 27 Jul 2004 11:39:08 +0900, Luke A. Kanies <luke@madstop.com> wrote:

[#3234] Re: Core support for Gems, and namespace — "Luke A. Kanies" <luke@...> 2004/07/27

On Tue, 27 Jul 2004, Austin Ziegler wrote:

[#3238] Re: Core support for Gems, and namespace — Austin Ziegler <halostatue@...> 2004/07/27

On Wed, 28 Jul 2004 00:14:29 +0900, Luke A. Kanies <luke@madstop.com> wrote:

Re: Reporting RI-documentation corrections ?

From: Johan Holmberg <holmberg@...>
Date: 2004-07-07 10:04:42 UTC
List: ruby-core #3149
On Wed, 7 Jul 2004, Dave Thomas wrote:
> On Jul 6, 2004, at 18:58, Lothar Scholz wrote:
>
> > Hmm using Array.flatten as an example method is maybe not very
> > clever.  You should take something that has a "call-seq" and
> > uses that special directive.
>
> Yeah - at the time I wrote that documentation call-seq didn't exist. I
> added it to the description, but should probably add it to the top as
> well.
>

Nice to know that there is a source where one can look for info
about how to write rdoc entries for C code.

After seeing the latest addition (with "call-seq"),

     ...
     * call-seq:
     *   cfg.read_value(key)            -> value
     *   cfg.read_value(key} { |key| }  -> value
     ...

I want to ask:
Should it be '->' or '=>' to indicate the return values?

In the current Ruby source (e.g. "array.c") both forms are used.
Does the difference have any significance, or should all entries
change to using  '->' ?

/Johan Holmberg


In This Thread