From owner-freebsd-current Sun Jul 28 09:24:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA29259 for current-outgoing; Sun, 28 Jul 1996 09:24:09 -0700 (PDT) Received: from kropotkin.gnu.ai.mit.edu (kropotkin.gnu.ai.mit.edu [128.52.46.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA29253 for ; Sun, 28 Jul 1996 09:24:07 -0700 (PDT) Received: by kropotkin.gnu.ai.mit.edu (8.6.12/8.6.12GNU) id MAA12670; Sun, 28 Jul 1996 12:23:54 -0400 Date: Sun, 28 Jul 1996 12:23:54 -0400 Message-Id: <199607281623.MAA12670@kropotkin.gnu.ai.mit.edu> To: bde@zeta.org.au CC: current@freebsd.org In-reply-to: <199607281510.BAA23418@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 29 Jul 1996 01:10:43 +1000) Subject: Re: `const char rcsid[]' vs -traditional From: Joel Ray Holveck Reply-to: joelh@gnu.ai.mit.edu 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. > They're designed to work with both K&R and ANSI compilers. Why is that? > I only object to breaking backwards compatibility by being sloppy - > it should be broken on purpose. I'll go along with that. -- http://www.wp.com/piquan --- Joel Ray Holveck --- joelh@gnu.ai.mit.edu The number you have reached is an imaginary number. Please rotate your phone 90 degrees and try again.