Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!galileo.berkeley.edu!jbuck From: jbuck@galileo.berkeley.edu (Joe Buck) Newsgroups: comp.lang.c++ Subject: Re: What C++ Compiler should I buy? Message-ID: <39549@ucbvax.BERKELEY.EDU> Date: 14 Nov 90 01:18:34 GMT References: <3072@lectroid.sw.stratus.com> <39546@ucbvax.BERKELEY.EDU> <17523@thorin.cs.unc.edu> Sender: usenet@ucbvax.BERKELEY.EDU Reply-To: jbuck@galileo.berkeley.edu (Joe Buck) Lines: 15 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. But there is no "standard library". You can call what you got from AT&T "standard" if you wish, but each vendor (including those who port cfront to different architectures) puts a different set of capabilities in their "standard library". There are things in libg++ that AT&T doesn't supply, similarly for all the others. Most of iostream's functionality is supported by stream, in any case. -- Joe Buck jbuck@galileo.berkeley.edu {uunet,ucbvax}!galileo.berkeley.edu!jbuck