|Pathologically Eclectic Rubbish Lister|
|( #3333=superdoc: print w/replies, xml )||Need Help??|
I claim that the two conditions don't look the same. They do to the compiler of course, but not to me.
In this case the second tells me the intent of the command whereas the first only tells me the command.
The purpose of the extra parentheses isn't to instruct the compiler, it is to instruct me. And it's not to instruct me in what specific sequence of operations the compiler is being told to execute, but to tell me something about the real problem being solved, i.e. 'is the point in the box?'.
And this is a diferent question than 'Is X both less than the maximum x and greater than the minimum x while at the same time, Y is less than the maximum y and greater than the mimimum y?'
You may ask, well, if the compiler thinks they're the same, then what's the difference? Or you may not, but let's assume you did. :)
I answer that source code is meant to be read by the compiler *and* humans. It therefore must serve two purposes, to correctly instruct the processor in the sequence of operations to be performed, and to instruct the human who reads it.
Many humans find 'Is the point in the box?' far more digestible than 'Is X less than ... and ... and ... '
For me, the 'documentary' parentheses make if far easier to see the question as an instance of the first and not the second.
In reply to Re: Re: Re: Operator Precedence