From: Robert Dober Date: 2009-01-05T05:43:30+09:00 Subject: [ruby-core:21121] Re: Definable != is a Bad Thing??? On Fri, Jan 2, 2009 at 12:42 PM, Kornelius Kalnbach wrote: > 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". You sure could def && a, &blk return blk.call if a a end and a && b is syntactic sugar for &&(a){b} Now I am not saying that this is a good idea, I am just saying that it can be done easily enough :) Cheers Robert -- It is change, continuing change, inevitable change, that is the dominant factor in society today. No sensible decision can be made any longer without taking into account not only the world as it is, but the world as it will be ... ~ Isaac Asimov