In article <20040608225817.GO1582@snowdrop.l8s.co.uk>,
David Laight <david@l8s.co.uk> wrote:
>> IMHO it would be more correct to always lint, and progs which are not
>> lint-clean (can't everything be made lint-clean?  With a few lint keywords to
>> ignore some errors, perhaps) can explicitly disable lint.
>
>And IMHO lint barfs at stuff which is perfectly legal C, and has to be
>silenced by adding casts which allow through code which ought to
>complained about.
>
>In particular having to cast one integral type to another leaves you
>open to accidentally supplying a pointer type.

You don't "have" to do this. A linted comment would work too.

christos