From: Dave Burt <burtdav@...>
Date: 2004-10-01T06:40:01+09:00
Subject: Re: Too Many Ways?

Sometimes I'm tempted to think this is already the way; in the doco for 
these duplicate methods, usually one will simply be a reference to the 
other. I think it would be nice if one was "canonical".

Bad example:
% ri Hash#each_pair
--------------------------------------------------------- Hash#each_pair
     hsh.each_pair {| key, value | block } -> hsh
------------------------------------------------------------------------
     Synonym for Hash#each.

"Gavin Kistner" <gavin@refinery.com> wrote:
> On Thu, 30 Sep 2004, Robert Klemme wrote:
>> If only the things that make life easier for newcomers could disappear
>> later, like training wheels on a bicycle.... :-)
>
> I suppose that's my wish, too. As unrealistic as it may be.
> ("Sorry, play time is over. All your existing code may crash and burn, but 
> in the end it'll make you a better programmer.")
>
> What I'd think was nice is if a bunch of things were officially 
> deprecated; no runtime warning (although perhaps with a -w or something) 
> but where exact duplicates exist, the King from on High would say "thou 
> shalt use #foo and not #bar". (I was even thinking of removing the 
> deprecated names from the documentation, but then that's no good for 
> someone needing to decipher existing code.)
>
(snip)