From: Kornelius Kalnbach <murphy@...>
Date: 2009-01-02T20:42:39+09:00
Subject: [ruby-core:21065] Re: Definable != is a Bad Thing???

Daniel Luz wrote:
> What I personally don't like about this is that it gives you a false
> sense of control. We still can't handle && and ||
the problem is short-circuit evaluation, I guess. this one should not
run the command:

  false && `rm -rf .`

it has to be part of the AST, and can't be changed at runtime. AFAIK,
you can't translate "a && b" into a method call in Ruby. they are more
like "and" and "or". the ternary operator (cond ? truecase : falsecase)
is another example - which is a shortcut for if-then-else. and you don't
want to redefine that ^^

> So, I liked the idea of leaving all the basic boolean logic
> outside of the language, since we don't have access to other key parts
> of it anyway.
we do: &, ^ and |, ~, and now ! can be redefined as you want. you
wouldn't expect to be able to redefine "not", "and", and such things.

[murphy]