From owner-freebsd-current  Sun Jul 28 08:16:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA26386
          for current-outgoing; Sun, 28 Jul 1996 08:16:04 -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 SMTP id IAA26364
          for <current@freebsd.org>; Sun, 28 Jul 1996 08:15:59 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id BAA23418; Mon, 29 Jul 1996 01:10:43 +1000
Date: Mon, 29 Jul 1996 01:10:43 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199607281510.BAA23418@godzilla.zeta.org.au>
To: bde@zeta.org.au, joelh@gnu.ai.mit.edu
Subject: Re: `const char rcsid[]' vs -traditional
Cc: current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  > Many sources no longer compile with non-ANSI compilers because
>  > they begin with const char rcsid[] = ...

>Why is this a concern?  These sources are designed for use with one
>system--- BSD--- and that comes with an ANSI compiler.  Admittedly,

They're designed to work with both K&R and ANSI compilers.

>something like this is easy enough to fix so it probably should be,
>but in general, is portability between compilers a priority with
>FreeBSD?

It is for 4.4BSD.  It isn't currently for FreeBSD, because all supported
systems (one :-) have an ANSI compiler.  I only object to breaking
backwards compatibility by being sloppy - it should be broken on purpose.

Bruce