X && Y || Z
binds operator precedence-wise as...
(X && Y) || Z

There are three suspicious cases of this in goodies

i.e.

source/filter.vcl/eps/eps.cxx
while ( ( --nSecurityCount ) && ( *pDest == ' ' ) || ( *pDest == 0x9 ) ) pDest++;

i.e. means...

while ( (( --nSecurityCount ) && ( *pDest == ' ' )) || ( *pDest == 0x9 ) ) pDest++;


source/filter.vcl/ieps/ieps.cxx
while ( ( --nSecurityCount ) && ( **pBuf == ' ' ) || ( **pBuf == 0x9 ) ) (*pBuf)++;

i.e. means

while ( (( --nSecurityCount ) && ( **pBuf == ' ' )) || ( **pBuf == 0x9 ) )
(*pBuf)++;

and

if( bEnlarge &&
    rCropLeftTop.Width() < 0 ||
    rCropLeftTop.Height() < 0 ||
    rCropRightBottom.Width() < 0 ||
    rCropRightBottom.Height() < 0 )

i.e. means

if( (bEnlarge &&
    rCropLeftTop.Width() < 0) ||
    rCropLeftTop.Height() < 0 ||
    rCropRightBottom.Width() < 0 ||
    rCropRightBottom.Height() < 0 )

Those meanings look very suspicious to me, I suspect that the intention is as
the attached patch changes them to be.