From owner-freebsd-current Sun Oct 20 12:50:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10806 for current-outgoing; Sun, 20 Oct 1996 12:50:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10801; Sun, 20 Oct 1996 12:50:50 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id FAA16430; Mon, 21 Oct 1996 05:47:03 +1000 Date: Mon, 21 Oct 1996 05:47:03 +1000 From: Bruce Evans Message-Id: <199610201947.FAA16430@godzilla.zeta.org.au> To: phk@FreeBSD.ORG, wollman@lcs.mit.edu Subject: Re: Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> If I have something like this: > >> typedef struct geom_req_s geom_req; > >> struct geom_req_s { >> ... >> }; > >Don't do that, then. It's horrid style anyway (IMAO), and you >/certainly/ don't see any native Berkeley code doing that. The style >guide should discourage the practice if it doesn't already. I agree. Typedef should only be used for scalar types and function types. Bruce