Xref:	news2.mv.net comp.os.msdos.djgpp:2705
From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: MikMod210 [Linking C and C++ together]
Date:	14 Apr 1996 08:30:46 GMT
Organization:	The National Capital FreeNet
Lines:	16
Sender:	ao950 AT freenet2 DOT carleton DOT ca (Paul Derbyshire)
Message-ID:	<4kqd3m$n1q@freenet-news.carleton.ca>
References:	<199604090947 DOT FAA22372 AT delorie DOT com> <4kiabu$evf AT news DOT cea DOT fr>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet2.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Eric NICOLAS (nicolas AT dsys DOT ceng DOT cea DOT fr) writes:
> So, when you use those include files as C-code, nothing special happens, BUT
> when you use those include files in C++ code, they will be delimited by
> 	extern "C" { ... }
> So old-C function names will be generated.

So THAT's what EXTERN "C" does! I've always wondered... it's in all the
djgpp .h files, presumably because they used c++ to write the libraries
such as libc and libpc.

--
    .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
 -()  <  circles, and bark is not smooth, nor does lightning travel in a
    `*'  straight line."    ,------------------------------------------------
         -- B. Mandelbrot  |  Paul Derbyshire (PGD) ao950 AT freenet DOT carleton DOT ca

- Raw text -