Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think.com!huxley!glenn From: glenn@huxley.huxley.bitstream.com (Glenn P. Parker) Newsgroups: comp.lang.c++ Subject: Re: What C++ Compiler should I buy? Message-ID: Date: 14 Nov 90 15:02:26 GMT References: <3072@lectroid.sw.stratus.com> <39546@ucbvax.BERKELEY.EDU> <17523@thorin.cs.unc.edu> Sender: glenn@huxley.UUCP Reply-To: (Glenn Parker) Distribution: comp Organization: Bitstream, Inc. Lines: 24 In-reply-to: leech@cezanne.cs.unc.edu's message of 13 Nov 90 23:04:16 GMT 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. Perhaps you should consider rephrasing your first sentence to say: "The lack of the iostream package makes G++ useless for many _existing_ applications that were written assuming it's presence." Since the original query was from someone who has not written a single line of C++ code yet, this hardly seems like a prohibitive constraint. Personally, I don't use the iostreams library, even though it comes with my compiler. In the absence of an ANSI standard, asserting that any C++ compiler is "useless" because it lacks a library provided by one vendor is simply short-sighted (and rather bigoted, IMHO). -- Glenn P. Parker glenn@bitstream.com Bitstream, Inc. uunet!huxley!glenn 215 First Street BIX: parker Cambridge, MA 02142-1270