Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!milano!cadillac!vaughan@mcc.com From: vaughan@mcc.com (Paul Vaughan) Newsgroups: comp.lang.c++ Subject: Re: What C++ Compiler should I buy? Message-ID: <13154@cadillac.CAD.MCC.COM> Date: 14 Nov 90 16:07:01 GMT References: <3072@lectroid.sw.stratus.com> <39546@ucbvax.BERKELEY.EDU> <17523@thorin.cs.unc.edu> Sender: news@cadillac.CAD.MCC.COM Reply-To: vaughan@mcc.com (Paul Vaughan) Organization: MCC VLSI CAD Program Lines: 22 In-reply-to: leech@cezanne.cs.unc.edu (Jonathan Leech) From: leech@cezanne.cs.unc.edu (Jonathan Leech) 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. No, but it is an interesting way of locking in customers. Fortunately, I don't believe AT&T intends to use it that way. I'd heard that AT&T had made or intends to make their library (or parts of it) available as a separate product. Can anyone confirm/deny that? Also, since I'm quoting out of context, I want to make sure that people are aware that g++ has two (at least) streams packages available (one in libg++, another from InterViews), both of which are similar to the AT&T streams package that came with their 1.2 release. I'm not aware of an AT&T streams 2.0 lookalike from any other vendor who didn't get it from AT&T. I don't know if g++ can compile AT&T's streams 2.0 package without difficulty, but it does support MI. The two compilers are not object-code compatible. Paul Vaughan, MCC CAD Program | ARPA: vaughan@mcc.com | Phone: [512] 338-3639 Box 200195, Austin, TX 78720 | UUCP: ...!cs.utexas.edu!milano!cadillac!vaughan