[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: Array Documentation Issues

From: Yukihiro Matsumoto <matz@...>
Date: 2005-12-20 18:58:04 UTC
List: ruby-core #6967
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.

In This Thread