Issue #19545 has been updated by jeremyevans0 (Jeremy Evans). Tracker changed from Bug to Feature Backport deleted (2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN) Not all Ruby code is allowed directly as a method argument. You can surround the code with parentheses to allow it, so `puts((false or not false))` works. This is a similar issue as `puts(raise rescue false)`, but not exactly the same. It may be possible to work around by modifying the parser to make `paren_args` handle this case (you could only handle this for method calls with explicit parentheses, since `puts false or not false` is already parsed as `puts(false) or (not false)`. However, I haven't attempted that, and it might result in parser conflicts. In terms of `puts not false`, that might also be possible to, though trickier (maybe `call_args`). However, as you mentioned, usage with commas may be problematic, and it would be a bad idea to support this only for single argument calls, so unless you could get it working with multiple arguments, it doesn't seem worth changing. In general, you should use `&&`, `||`, and `!` for these cases. `and`, `or`, and `not` are designed with control flow in mind (e.g. `method1 arg or method2` as opposed to `method arg1 || arg2`). I don't think the current behavior is a bug, switching to feature request. ---------------------------------------- Feature #19545: lp/hp logic parsing inconsistency https://bugs.ruby-lang.org/issues/19545#change-102627 * Author: hurricup (Alexandr Evstigneev) * Status: Open * Priority: Normal ---------------------------------------- As far as i get it, low precedence logic should behave the same as high precedence. But: This is ok: ``` puts(false || !false) ``` And this is not: ``` puts(false or not false) ``` Feels like in latter case there is some mess with comma precedence. -- https://bugs.ruby-lang.org/