Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rlgvax!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.unix-wizards
Subject: Re: C++ installation
Message-ID: <326@hadron.UUCP>
Date: Sat, 22-Mar-86 11:28:02 EST
Article-I.D.: hadron.326
Posted: Sat Mar 22 11:28:02 1986
Date-Received: Tue, 25-Mar-86 03:24:24 EST
References: <1762@brl-smoke.ARPA>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 26
Summary: (only stdio.h answer)

In article <1762@brl-smoke.ARPA> jon@csvax.caltech.edu (Jonathan P. Leech) writes:
>    the   order   of   members	 in   a   FILE	 is   different    for
>    /usr/include/stdio.h  and  the  supplied  stdio.h  for  C++.   The
>    documentation claims this should only be true for non  System  Vs.
>    Is it sufficient to change the C++ header?

I've never used C++; but nobody else has responded, and I figured I'd
take on at least this.

If and only if C++ source files always compile with their very own
set of include files  a n d  libc.a, then you must leave the stdio.h
file as it is.  The FILE is only an in-core representation, and
doesn't correspond to anything in the external environment.  However,
as I understand it, C++ is only a pre-processor, and relies on cc to
do the rest of its work.  In that case (and assuming you're not talking
about just compiling c++ itself), you must use the FILE structure that
is compiled into libc.a; i.e., the one in <stdio.h>.  If you have to
mix a C++ library (that uses FILE's) and your native C library ...
you're out of luck.

I suspect you may have known this; I post this just in case you didn't,
and to  prime the pump.  You may get better response by re-posting to
net.c++.
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}