From: Josh Cheek <josh.cheek@...>
Date: 2011-03-09T03:25:42+09:00
Subject: Re: Duplicate methods removal in Ruby's TODO ?

--0023545309706ef1d1049dfcbaec
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 8, 2011 at 12:12 PM, Adam Prescott <mentionuse@gmail.com> wrote:

> On Tue, Mar 8, 2011 at 1:12 PM, Joey Zhou <yimutang@gmail.com> wrote:
>
> > These methods all alert the receiver in place. They have no trailing
> > exclamation mark because there are no methods of the same name which
> > return a modified copy of the object only. I don't think a bang is an
> > alarm to tell you "there is a same name method", a bang should be an
> > alam "it will change your object, be carefull!" So string.clear should
> > be string.clear!, even if there's no "clear" method which doesn't alert
> > the receiver. I think it's logical.
> >
>
> Using bang names to denote receiver-modifying methods is not the
> convention,
> and I don't think it should become it.
>
> http://dablog.rubypal.com/2007/8/15/bang-methods-or-danger-will-rubyist
>

I think it should become the convention. I consider the bang to be nearly
meaningless as is.

--0023545309706ef1d1049dfcbaec--