From: Cameron McBride <cameron.mcbride@...>
Date: 2005-03-23T17:21:51+09:00
Subject: Re: RCR 296: Destructive methods return self

> Then perhaps its time to just go all the way and support an in place
> construction (umm... destruction ;-) on any method. Put the bang where
> the dot is.
> 
>   if a!strip.unmodified?

I'm not a CS guy, nor a language designer - but this looks intriguing.
 It'd be a way for the ruby programmer to signal that the upcoming
chain should be optimized and destructive and leave the how (or if) up
to the interpreter.

Course, I also like the Kernel#wtf!? if one needs a boolean value and
have any destructive method return self.  It makes sense, and seems to
go with a lot of the ruby way as I see it.  (and it's not half as ugly
as @@vars).

Cameron