Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!ll-xn!husc6!seismo!nbires!isis!udenva!wedgingt
From: wedgingt@udenva.UUCP
Newsgroups: comp.lang.c++
Subject: Re: Standard system header files for non-System V environments?
Message-ID: <3770@udenva.UUCP>
Date: Tue, 2-Jun-87 22:07:13 EDT
Article-I.D.: udenva.3770
Posted: Tue Jun  2 22:07:13 1987
Date-Received: Sat, 6-Jun-87 04:24:52 EDT
References: <736@daimi.UUCP>
Reply-To: wedgingt@udenva.UUCP (Will Edgington)
Distribution: world
Organization: U of Denver
Lines: 30

In article <736@daimi.UUCP> pederch@daimi.UUCP (Peder Chr. N|rgaard) writes:
>But this causes some minor problems for people who work in other environments
>like BSD 4.n and, even worse, MS-DOS. One problem is that it is some work to 
>build up a complete set of C++ header files from the C header files and
>the descriptions of function parameters in the manuals. Another problem
>is that is error-prone. The worst problem is that the result is not unique,
>at least not when you come to some more complicated system interfaces,
>like the SunView system from Sun Microsystems. So if you use your own
>C++ header files you risk end up with a program which is not even source
>level portable to another perfectly identical system.

I'm missing something.  90% of the work involved is converting the
function declarations to include the types of the arguments, right ?
If not, maybe someone should post what the other major change(s) is.

If yes, why not write a program that takes the human-readable lint
libraries and massages them into the correct C++ #include files ?
The messiest part here is dealing with functions that take a variable
number of arguments, but don't use the "varargs" methods.

Then the option ('-C' on BSD) most (all ?) lints have to *create*
the human readable lint libraries (from the original C source) can
be used to go all the way from C to C++ declarations (assuming the
C functions were reasonably well defined, argument-wise) ...
-----
Will Edgington, Computing and Information Resources, University of Denver
System Administrator for udenva (== dueos), dutyche, duorion, dunike, ...
{{hplabs,seismo}!hao,ucbvax!nbires,boulder,cires,ssds}!udenva!wedgingt,
WEDGINGT@DUCAIR (BITNET), wedgingt@ccndu (CSN/CCN), ...
COMING SOON: wedgingt@du.edu (all nets)|"No two addresses are the same ..."