Xref: utzoo comp.std.c:99 comp.lang.c:10932 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!athena.mit.edu!raeburn From: raeburn@athena.mit.edu (Ken Raeburn) Newsgroups: comp.std.c,comp.lang.c Subject: Re: __STDCPP__ anybody? Message-ID: <5924@bloom-beacon.MIT.EDU> Date: 27 Jun 88 02:59:53 GMT References: <2459@plus5.UUCP> <8101@elsie.UUCP> Sender: daemon@bloom-beacon.MIT.EDU Reply-To: raeburn@athena.mit.edu (Ken Raeburn) Organization: Massachusetts Institute of Technology Lines: 12 On a vaguely related note, is there any way of distinguishing at compile time between a hosted and a standalone implementation? The __STDC__ macro says you've got at least standalone, but how do you know if you can assume a fully-conforming hosted implementation? (At least, you can rely on __STDC__ if the compiler isn't fooling you. Maybe someday Metaware will get it right....) The alternative to utilizing the hosted environment would presumably be to supply your own support routines. (Hm, there's a question. If you're on a standalone implementation, are the library procedure names still considered reserved?)