From owner-freebsd-hackers  Tue May  6 10:50:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA24102
          for hackers-outgoing; Tue, 6 May 1997 10:50:56 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA24096
          for <hackers@FreeBSD.ORG>; Tue, 6 May 1997 10:50:53 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id DAA26819; Wed, 7 May 1997 03:46:35 +1000
Date: Wed, 7 May 1997 03:46:35 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199705061746.DAA26819@godzilla.zeta.org.au>
To: bde@zeta.org.au, rb@gid.co.uk
Subject: Re: /usr/include/ftpio.h is not C++ safe
Cc: gclarkii@main.gbdata.com, hackers@FreeBSD.ORG, jkh@time.cdrom.com,
        nadav@barcode.co.il
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I have *shitloads* of old code around (mostly in clients' systems) which
>breaks in subtle and mysterious ways when naively ported to ANSI C. It
>often boils down to ANSI having broken the portability of comparing chars
>with constants [don't get me started, it's a couple of years since I had a
>good rant about that one :-)].
>
>-traditional is a life-saver.

gcc -traditional supports prototypes, so this is no argument for __P(())
:-).  It's an argument agains __P(()) - it's reasonable for headers to
only support the compiler(s) shipped with the system.

Bruce