Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!haven!decuac!bacchus.pa.dec.com!news.crl.dec.com!decvax.dec.com!zinn!nuucp
From: mjv@objects.mv.com (Michael J. Vilot)
Newsgroups: comp.lang.c++
Subject: Re: standard library (was: What C++ Compiler should I buy?)
Message-ID: <1018@zinn.MV.COM>
Date: 21 Nov 90 18:42:59 GMT
Sender: nuucp@zinn.MV.COM
Lines: 20

Paul Vaughn mentioned:
> I'm not aware of an AT&T streams 2.0 lookalike from any other vendor
> who didn't get it from AT&T.
Steve Clamage did an independent iostreams implementation for TauMetric.  He is
helping X3J16 define an I/O library that is implementable.  The standard I/O
library is based on iostreams (i.e. AT&T 2.0), with suggestions for simplifying
it from Jerry Schwarz, Doug Lea, and others.  One comment we received last week
helped us remove the Unix-specific file descriptors (as `int's), so a vendor 
trying to provide a C++ implementation on an IBM 370 system could do so.

Our goals for the standard streams classes are to remain compatible with the
iostreams version, while removing some of the difficulties posed by multiple
inheritance, and to define `conformance' and extensibility in a way that the
existing streams libraries could be declared `legal' implementations without
too much rework.  In this way, we should be able to provide an effective
solution with the least disruption to both users and library providers.

--
Mike Vilot,  ObjectWare Inc, Nashua NH
mjv@objects.mv.com  (UUCP:  ...!decvax!zinn!objects!mjv)