From owner-freebsd-hackers  Sat Oct 14 15:52:00 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA21412
          for hackers-outgoing; Sat, 14 Oct 1995 15:52:00 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA21395
          for <freebsd-hackers@FreeBSD.org>; Sat, 14 Oct 1995 15:51:56 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA28055; Sun, 15 Oct 1995 08:50:34 +1000
Date: Sun, 15 Oct 1995 08:50:34 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199510142250.IAA28055@godzilla.zeta.org.au>
To: freebsd-hackers@FreeBSD.org, j@uriah.heep.sax.de
Subject: Re: lint
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

>> >. The ANSI-violating definitions for fgets() (second parameter must be
>> >  int, not size_t) and ftell() (parameter is not const); i'm about to

>They are benign, and only become apparent by manually declaring the
>functions according to the ANSI standard.  Jochen Pohl's llib-lstdc
>does this.

I first notice the `const' problem in libpthreads it 1.1.5.  It implemented
ftell() correctly (though it's not incorrect to not modify the parameter)
but I somehow misread the standard and thought that it was libpthreads that
was wrong.

>The newly-built lint buried another bogon out of the depths of the
>header mishmash: we've got a name clash for struct pmap!  It's
>declared inside the VM stuff as a "page map" structure
>(machine/pmap.h), and inside the RPC library as a "portmapper"
>structure.  The header files for both are required to have a complete
>set of header files describing the libc.

One way to find more bogons than you want to know about is to include
all headers.  Another way is to change all typedefs in headers to ones
that are allowed by standards but weird.  Portable applications should
still compile cleanly with maximal warnings enabled.

Bruce