From: Yukihiro Matsumoto <matz@...>
Date: 2005-12-21T03:58:04+09:00
Subject: Re: Array Documentation Issues

Hi,

In message "Re: Array Documentation Issues"
    on Wed, 21 Dec 2005 01:46:41 +0900, James Edward Gray II <james@grayproductions.net> writes:

|Let's start with:
|
|$ ri -T Array.indices
|---------------------------------------------------------- Array#indices
|      array.indexes( i1, i2, ... iN )   -> an_array
|      array.indices( i1, i2, ... iN )   -> an_array
|------------------------------------------------------------------------
|      Deprecated; use Array#select.
|
|To me, that reads similar to "Bathtub out-of-order, use nearest  
|sink."  Can we switch that to
|"use Array#values_at"?  I think that's a much closer fit.

This is a bug in a document.  I will fix it soon.

|Then we have:
|
|$ ri -T Array.initialize_copy
|-------------------------------------------------- Array#initialize_copy
|      array.replace(other_array)  -> array
|------------------------------------------------------------------------
|      Replaces the contents of self with the contents of other_array,
|      truncating or expanding if necessary.
|
|         a = [ "a", "b", "c", "d", "e" ]
|         a.replace([ "x", "y", "z" ])   #=> ["x", "y", "z"]
|         a                              #=> ["x", "y", "z"]
|
|I'm not sure what that was *suppose* to say, but I'm betting (and  
|hoping) it wasn't that.

This is caused by RDoc.  I'm not sure how we can handle.

							matz.