> My opinion only.
> 
> It's an obscure feature, very rarely needed, 
> and it is not intuitive that such a feature
> would even be there.

And how does that make it "awkward"?  That's all I'm asking. EVERY
feature is going to be intuitive for some and not others, so I don't
think that that's relevant.

I find it awkward that many ! methods return nil sometimes STRICTLY
so that I can't chain them.

Again, I'm not arguing for its insertion to the library; I can add it
myself if I need it.  I'm simply (still) curious as to why anyone
would consider this some hinderance to their coding.  

Or am I misreading "awkward"?

I'll shut up on it now, as it's not really worth the discussion.

__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com