Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: prototyped system include files (was: Re: extern "C")
Message-ID: <2389@lupine.NCD.COM>
Date: 3 Nov 90 03:53:48 GMT
References: <1990Oct10.062518.23722@cs.nott.ac.uk> <13870@ulysses.att.com>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 27

In article <13870@ulysses.att.com> ggs@ulysses.att.com (Griff Smith) writes:
<In article <1990Oct10.062518.23722@cs.nott.ac.uk>, gas@cs.nott.ac.uk (Alan Shepherd) writes:
<> 
<> I've had several responses to my original question about extern "C"...
<> ... However, all the solutions seem to rule out the possibility of using C
<> header files within C++.
<> 
<> Alan Shepherd
<
<I'm not sure what you're basing this on, since AT&T C++ 2.0 uses
<standard C header files inside C++ wrappers that discard the useless C
<function definitions.  If you have seen this solution and object to the
<aesthetics, so be it.  Given that the wrapper would be necessary anyway
<to supply declarations with full type checking, I find it hard to
<quibble about the details.

One alternative solution to the problems that people seem to have with
system include files which are not fully prototyped is to use my
protoize program to get them prototyped.

For more details, send me E-mail.

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.