Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!jimad
From: jimad@microsoft.UUCP (Jim ADCOCK)
Newsgroups: comp.lang.c++
Subject: Re: ansi c output from cfront(s)
Message-ID: <56876@microsoft.UUCP>
Date: 23 Aug 90 21:57:50 GMT
References: <9008181728.3322@nowhere.uucp> <58170030@hpclscu.HP.COM>
Reply-To: jimad@microsoft.UUCP (Jim ADCOCK)
Organization: Microsoft Corp., Redmond WA
Lines: 15

In article <58170030@hpclscu.HP.COM> shankar@hpclscu.HP.COM (Shankar Unni) writes:
|>    void __dt__3fooFv(struct foo *__0this, int );
|> the only "ansi c" compiler I have available to me (Microsoft C 6.0) chokes on
|> this. Which has the bug, the cfront(s) or MSC?
|
|Actually, both.
|
|MSC is the more glaring violator, because the ANSI C standard explicitly
|allows you to leave out parameter names on any of the parameters (i.e.
|parameter names for external function declarations are totally optional,
|and there is no requirement for them to be all present or all absent).

The MSC people are aware of this difference from the ANSI spec, and it will 
be corrected by release 7.0 -- if not earlier.  I will update this info if I 
can find out more exact details.