Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!cs.utexas.edu!uunet!microsoft!jimad
From: jimad@microsoft.UUCP (Jim ADCOCK)
Newsgroups: comp.lang.c++
Subject: Re: What C++ Compiler should I buy?
Message-ID: <59190@microsoft.UUCP>
Date: 20 Nov 90 00:30:36 GMT
References: <sean.657840642@s.ms.uky.edu> <3072@lectroid.sw.stratus.com> <39546@ucbvax.BERKELEY.EDU> <17523@thorin.cs.unc.edu>
Reply-To: jimad@microsoft.UUCP (Jim ADCOCK)
Organization: Microsoft Corp., Redmond WA
Lines: 14

In article <17523@thorin.cs.unc.edu> leech@cezanne.cs.unc.edu (Jonathan Leech) writes:
>	You can quibble over terminology, but the fact is that lack of the
>iostream package makes G++ useless for many applications, such as mine. In
>terms of portability, the standard library is part of the language.

regards ANSI-fication "standards" -- I believe the libraries group of
the standardization committee is working to identify a simplified version
of iostreams to become the "standard."  What this is exactly, is not
yet finalized, I believe.  It sounds like the intent is to make stdio call
freely intermixable with streams calls, so maybe one would do best for today
to stick to the simpler functionality of [io]/streams, and use stdio
for more complicated functionality.  --Thus making it more likely that
your software will work with the future ANSI library standards -- when
they emerge.