[#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: [doc-patch] Another rdoc formatting error in array.c

From: Johan Holmberg <holmberg@...>
Date: 2004-07-12 15:54:30 UTC
List: ruby-core #3174
On Mon, 12 Jul 2004, H.Yamamoto wrote:
>
> Johan Holmberg <holmberg@iar.se> wrote:
> (2004/07/11 02:09)
>
> >I have discovered yet another formatting error that I missed the
> >previous time. See the patch below.
>
> I merged your patch to mine. Now looks more consistent. Would you check this?
>

In general I think the changes are in the right direction (but I'll
print out a newly generated version an look at it in detail, and
maybe supply further comments later).

As I understand your diff you have:

- used 'index' as parameter name systematically
  (instead of 'i' and 'int' ...)
- used "#" to denote method names instead of "." (as in Array#each)
- used "array" systematically for the receiver in the
  call-seq of a method (instead of "self" sometimes earlier)
- used "self" for the receiver in the text describing a method
- misc. other cleanups

But I still notice some remaining inconsistencies. For example:

- sometimes "arr" is used instead of "array"
- sometimes methods are written as "Array#at" and sometimes as
  "<code>Array#each</code>".

I don't know what is the right way for method references, but at a
glance I think the alternative with <code>...</code> looks better.

/Johan Holmberg


In This Thread