🚀 go-pugleaf

shekar@gizmo.cs.msstate.edu (Shekar Ramanathan) wrote:
>Max Welton (maxw@lmsc.lockheed.com) wrote:
[snip]
>What you should do is have another file called foo.c and compile it using
>a K&R C compiler.  In main.C, you should just include a prototype declaration
>for foo and finally link them together.
>
>foo.c
>int foo(boo)
>    int boo;
>{
>   return boo;   
>}
>
>main.C:
>
>extern "C"{
>	int foo();
>}
>int main()
>{ cout << foo(0) << endl; }
>
>
>Shekar

I have the same problem with or without the 'extern"C"'. In the 
real-world case, "foo.h" is a 3rd-party vendor header. We're just 
not in a position to rewrite our favorite vendor's K&R headers.

I was hoping that g++ could be cajoled somehow into the behaviour 
of our HP cfront compiler in this case:

  CC -c main.C
  CC: "main.C", line 4: warning: old style definition of foo() (anachronism) 
  (1386)

  Compilation finished at Mon Nov 27 11:35:38

Not there yet...

--
Max Welton, CMST (Coordinator of Many Small Things)
   maxw@lmsc.lockheed.com
   maxw@ix.netcom.com