From owner-freebsd-current Wed Aug 23 16:07:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id QAA29506 for current-outgoing; Wed, 23 Aug 1995 16:07:09 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id QAA29500 for ; Wed, 23 Aug 1995 16:07:06 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id QAA10616; Wed, 23 Aug 1995 16:05:31 -0700 From: "Rodney W. Grimes" Message-Id: <199508232305.QAA10616@gndrsh.aac.dev.com> Subject: Re: pedantic paul on compilation warnings To: jfieber@grendel.csc.smith.edu (John Fieber) Date: Wed, 23 Aug 1995 16:05:31 -0700 (PDT) Cc: pst@shockwave.com, current@freebsd.org In-Reply-To: <199508232257.RAA06762@fieber-john.campusview.indiana.edu> from "John Fieber" at Aug 23, 95 05:57:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 976 Sender: current-owner@freebsd.org Precedence: bulk > > Paul Traina writes: > > ...and most disturbingly, something has either gone very wrong with groff > > and its macro packages, or we're getting really sloppy in the documentation. > > Either the documentation was bad from the beginning, or something > is up with groff/macros. I don't think anybody has touched the docs. > I'm not a [gtn]roff expert, (or even novice to be truthful) so I > wouldn't bee too good at debugging. However, a quick scan would > indicate that a great bulk of the warnings fall in just a few > problem categories so it may not be quite as big of a job... > (but then again, it might) Major part of the problem here is some one replaced the 4.4BSD provided macro sets with the groff ones. The groff ones are not up to snuff for the BSD documentation, which used BSD specific hacks :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD