> That depends on the reader, and as we have multiple readers, it is better to > be consistent. And, I find no ambiguity on IN_RANGE, it is > inclusive for both values and used heavily through the compiler, so using it > is a welcome cleanup, e.g. some ports that use it most often:
OK, let's go for IN_RANGE then, but it's Yoda style on steroids! -- Eric Botcazou