Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!usc!apple!uokmax!occrsh!att!cbnewsm!gregk
From: gregk@cbnewsm.att.com (gregory.p.kochanski)
Newsgroups: comp.lang.c++
Subject: Re: ansi c output from cfront(s)
Message-ID: <1990Aug20.130642.22720@cbnewsm.att.com>
Date: 20 Aug 90 13:06:42 GMT
References: <9008191857.13779@nowhere.uucp>
Distribution: usa
Organization: AT&T Bell Laboratories
Lines: 24

In article <9008191857.13779@nowhere.uucp> sking@nowhere.uucp (steven king) writes:
>
>in my earlier post about MSC choking on the output of cfront
>(Guidelines || Intek) using the +a (ansi c) switch, I think I wasnt clear
>about what MSC didnt like; protos generated by cfront of the form
>
>	void __dt__3fooFv(struct foo * __0this, int );
>
>cause MSC to complain "syntax error : ')' " for the line in question;
>appearently it expecting a tag for the second arguement. Editing the output
>of cfront to produce
>
>	void __dt__3fooFv(struct foo * __0this, int free);
>
>and MSC compiles it without a complaint.

I found this a while back.  It is a bug in Microsoft C, as ANSI standards
specify both of the above prototypes to be allowable.  I am told there
is a simple change to make to cfront which suppresses all variable
names in prototypes, but unless you have the source code, you're out
of luck.

Greg Kochanski   gpk@physics.att.com
AT&T Physics Research -- Physics for fun and profit.