Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!julius.cs.uiuc.edu!usc!samsung!uunet!lotus!lotus.com!sng
From: sng@steveng.lotus.com (Stephen Ng)
Newsgroups: comp.sys.next
Subject: Re: C++ and <stdio.h> -- Bug report
Message-ID: <SNG.91Jan28113214@steveng.lotus.com>
Date: 28 Jan 91 16:32:14 GMT
References: <u-1Gbp*6@cs.psu.edu>
Sender: news@lotus.com
Distribution: comp
Organization: /sng/.organization
Lines: 20
In-Reply-To: melling@cs.psu.edu's message of 26 Jan 91 05:35:14 GMT

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);

Actually, NeXT did a fair amount of testing on C++, and I know of one beta
tester who developed a large commercial application in C++.  

To use the include files, you must put the following in your source code:

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

This turns off C++ keywords while the file stdio.h is being processed.  It also
tells the compiler to use C linkage for the library functions in stdio.h.