Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!ub!oswego!news From: dl@g.g.oswego.edu (Doug Lea) Newsgroups: comp.lang.c++ Subject: Re: iostream question Message-ID: Date: 26 Aug 90 10:10:54 GMT References: <127@tdatirv.UUCP> <2667@dataio.Data-IO.COM> Sender: news@oswego.Oswego.EDU (Network News) Reply-To: dl@g.oswego.edu Organization: SUNY Oswego Lines: 30 In-reply-to: bright@Data-IO.COM's message of 24 Aug 90 18:27:22 GMT Walter Bright says: > [...] > First, iostreams is not part of > the C++ standard as defined by the ARM. The ARM does not mention iostreams. > Second, a large part of the functionality of iostreams is contained in > the header files (one tendency of C++!). A large part of the functionality > is also not available as a specification. This means that in order to > clone iostreams, we'd have to largely plagarize AT&T's code, which is > copyrighted. > [...] > We do not wish to steal AT&T's proprietary code. > [...] > Zortech is committed to fully supporting the evolving ANSI C++ standard > and will implement an iostreams to Jerry's new spec. (or rather, the ANSI libraries committee's new spec). Otherwise, ditto for the GNU C++ library (libg++). One of the most interesting questions about all this is the impact of exception support on the design and implementation of stream classes. -Doug -- Doug Lea, Computer Science Dept., SUNY Oswego, Oswego, NY, 13126 (315)341-2688 email: dl@g.oswego.edu or dl@cat.syr.edu UUCP :...cornell!devvax!oswego!dl or ...rutgers!sunybcs!oswego!dl