From: Brian Mitchell Date: 2006-03-17T04:49:16+09:00 Subject: Re: [ ruby-Bugs-3843 ] "not" operator used in expression that is a method parameter can generate syntax error On 3/16/06, mathew wrote: > I still don't understand why foo(!(1<2)) is OK, but foo(not(1<2)) isn't. > > The pickaxe says that the only difference between '!' and 'not' is > precedence, and in these two cases everything is explicitly bracketed so > precedence shouldn't be involved. > > What am I missing? foo(not(1<2), 3) or more clearly bound if I understand Matz correctly: foo(not((1<2),3)) not has meaningless semantics in this case. If not was allowed only in single argument calls, this might lead to confusion. Brian.