Klaus Darilion writes:
if
(!enum_query("e164.arpa") && !enum_query("e164.info")
&&
!enum_query("freenum.org")) {
route(PSTN)
}
This may cause unpredictable behaviour, as you never know how the if
statement is processed internally. (which lookup will be the first
one)
this is news to me. i have always thought that && in ser.cfg has same
semantics as in C, i.e., that operands are evaluated from left to
right. is it really true that they can be evaluated in any order?
I've never found this somewhere written down, thus I avoided such
constructs. If the behaviour is specified, then it is save to use.
regards,
klaus