Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!msuinfo!news
From: erickson@frith.egr.msu.edu (Carl Erickson)
Newsgroups: comp.sys.next
Subject: Re: C++ and <stdio.h> -- Bug report
Message-ID: <1991Jan28.200219.23993@msuinfo.cl.msu.edu>
Date: 28 Jan 91 20:02:19 GMT
References: <u-1Gbp*6@cs.psu.edu>
Sender: news@msuinfo.cl.msu.edu
Reply-To: erickson@egr.msu.edu (Carl Erickson)
Distribution: comp
Organization: Michigan State University
Lines: 30

In article <u-1Gbp*6@cs.psu.edu> melling@cs.psu.edu (Michael D Mellinger) writes:
>
>
>NeXT uses the C++ reserved word 'new' in stdio.h!!!!!  I can't believe
>NeXT didn't catch this!!!  Arrggh.  I guess no one at NeXT actually
>uses C++.
>
>The simple fix:  
>
>extern int rename(const char *old, const char *_new);
>
>
>
>-Mike

I got some help from NeXT on this problem.  All you need to
do is

extern "C" {
#include <stdio.h>
}

and you tell the C++ compiler that you will be using include
files for ANSI C.  This solves the sort of problem you had
with re-use of the keyword "new".

Carl

--
erickson@egr.msu.edu || uunet!frith!erickson || erickson@msuegr.bitnet