Status of 2.4 release
Russ Allbery
rra at stanford.edu
Mon Jan 13 20:51:43 UTC 2003
bill davidsen <davidsen at tmr.com> writes:
> Whatever, but let's not remove those needed to make lint or compilers
> shut up. The more warnings caused by non-errors the more likely a real
> problem will vanish in the noise.
The lint that we use is gcc with a bunch of warning flags, and I left in
the casts that are required for it (which are only in the casts in the
Perl interface code where, e.g., the return value of POPs() is ignored).
Any lint that can't deal with code like:
close(fd);
and requires that it be written as:
(void)close(fd);
isn't appropriate to use with INN. I can understand the coding style
where one always uses the latter, but I don't personally prefer it, and I
think it clutters the code unnecessarily. It's also (more persuasively)
not a coding style used by pretty much any other open source or free
software project that I've worked on, so people aren't used to it and
don't maintain it.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers
mailing list