Re: Short circuit boolean evaluation

[Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>]

svaa <svaa@ciberpiula.net> wrote:
: "Steve" <nospam_steved94@comcast.net> wrote in message news:<Vwjqb.115053$HS4.999172@attbi_s01>...
:> I consider it unimaginable to make such a fundamental change to a language
:> in order to save a few keystrokes when more than a few billion lines of
:> source code might be effected.
: 
: I wouldn't call it a few  keystrokes, I use it in every condition. 

Hm. That indicates that you are writing tons of complicated
conditionals? Without having seen the particular programming
problem, might it not be worth considering a different
aproach to soving the programming problem?

Even if programmer productivity could be increased by a fraction
of n.m more lines of code, say, by making short circuit evaluation
implicit, what syntax do you propose for full evaluation?

(I guess n is 0 and m is close to 0, but not that
n is 0 and then m is close to 0 ;-)

Georg