Re: short-circuit control forms (& 'long names are doom')

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

I wouldn't exactly call it "disgusting". There are situations in which it
makes sense. As was brought up elsewhere, when dealing with tight timing
considerations (efficiency being the reason this was brought up in the first
place) or high reliability requirements, you may want to force all
conditions to be evaluated to avoid timing variations and/or to increase
path coverage when testing.

I would agree that generally speaking, one would want to avoid side-effects
when writing conditional tests. This is the sort of abomination often seen
in C programs that makes it difficult to understand & debug the code. (Also
one of the reasons you had to "debug" it in the first place, rather than
just run it.) But avoidance is not exactly the same as "never". (Example:
"if (X = Pseudo_Random_Number (Something)) then...")

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Robert Dewar" <dewar@gnat.com> wrote in message
news:5ee5b646.0106221243.3617111a@posting.google.com...
> "DuckE" <nospam_steved94@home.com> wrote in message
news:<QGyY6.222270$p33.4459972@news1.sttls1.wa.home.com>...
> We never have a situation where both operands *must* be evaluated,
> since this would represent disgusting coding with side effects, so
> we do not have a rule that covers this case :-)