From owner-freebsd-current Mon Oct 21 15:23:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17985 for current-outgoing; Mon, 21 Oct 1996 15:23:07 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA17979; Mon, 21 Oct 1996 15:22:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA06727; Mon, 21 Oct 1996 15:20:19 -0700 From: Terry Lambert Message-Id: <199610212220.PAA06727@phaeton.artisoft.com> Subject: Re: To: jdp@polstra.com (John Polstra) Date: Mon, 21 Oct 1996 15:20:18 -0700 (MST) Cc: bde@zeta.org.au, current@FreeBSD.org, phk@FreeBSD.org, wollman@lcs.mit.edu In-Reply-To: <199610202112.OAA04687@austin.polstra.com> from "John Polstra" at Oct 20, 96 02:12:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Why do you say that? There's already precedent for using typedefs > for structs in, for example, the "DIR" type of . And it > is in line with C++ practice, where the struct, class, or union > keyword is almost never used outside of the declaration. (I know, > this is C, not C++. But the idea that the name of a type should > not carry unnecessary information about its representation is a > valid one.) Don't forget "FILE". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.