On 28 March 2012 07:53, Christos Zoulas <[email protected]> wrote:
> In article <[email protected]>,
> Valeriy E. Ushakov <[email protected]> wrote:
>>
>>But that is not what the code was.  The code was:
>>
>>    char c; if (c == CHAR_MAX) ...
>>
>>and *that* is portable.  As I said in another mail to thsi thread that
>>went unanswered, it is literally schizophrenic of lint to complain
>>about it.
>
> How can lint know that if (c == 255) is portable? Because CHAR_MAX
> gets expanded by cpp to 255 before lint parses the file.
>

(How) does the compiler (not) catch this one ?

-- 
~Cherry

Reply via email to