Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: C++ and ANSI C
Message-ID: <10213@smoke.BRL.MIL>
Date: 5 May 89 16:10:04 GMT
References: <12005@paris.ics.uci.edu> <44100029@hcx2> <1989May4.001911.3382@utzoo.uucp> <3934@tekcrl.LABS.TEK.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <3934@tekcrl.LABS.TEK.COM> danw@tekchips.LABS.TEK.COM (Daniel E. Wilson) writes:
>In article <1989May4.001911.3382@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes:
>> 1. "extern foo();" means (so to speak) "extern foo(...);" in ANSI C and
>> 	"extern foo(void);" in C++
>    Number 1 is incorrect since ...

Your explanation was okay, but it didn't contradict Henry's point,
which is correct.  "extern foo();" in source code has the different
meanings indicated in the two languages.  Henry's "(so to speak)"
was a warning that ANSI C doesn't actually support the C++ notation
he used in his explanation.  (Its similar-but-not-identical syntax
for variable-argument functions has yet a different meaning.)