From: Greg McIntyre <greg@...>
Date: 2003-11-20T08:17:16+09:00
Subject: Re: ! usage

"Brett H. Williams" <brett_williams@agilent.com> wrote:
> The above is doing a variable assignment with a method.  So the
> receiver is a different object after the method is called.

That's true...

So that's 1 reason against it so far. However ! does mean danger... :)


> This sounds undesirable.  I think of ! as either meaning danger OR
> operate on an existing object, but not this.
> 
> I'm not sure this is even possible in Ruby, but I know it violates my
> POLS:|

I must have a non-standard POLS. :) I can see this trend continuing, so
I'll happily stand down my idea. I don't like treading on other people's
POLS. I think really I just needed to understand the reasons behind !.
There's a long road between code being implemented and code being used
and sometimes the rationales get lost along the way.

-- 
Greg McIntyre ======[ greg@puyo.cjb.net ]===[ http://puyo.cjb.net ]===