From 4629547525107106330 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,cc1a555bbe9617a3 X-Google-Attributes: gidf78e5,public From: Valentin Bonnard Subject: Re: STL and SGI and strings Date: 1998/01/10 Message-ID: <34B6580F.6A50@pratique.fr>#1/1 X-Deja-AN: 314531050 Content-Transfer-Encoding: 7bit References: <34B57837.41C6@pixar.com> X-Original-Date: Fri, 09 Jan 1998 18:02:08 +0100 Mime-Version: 1.0 Reply-To: bonnardv@pratique.fr Content-Type: text/plain; charset=us-ascii Organization: Ecole Normale Superieure, Paris, France X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBFAgUANLbnxuEDnX0m9pzZAQEt2QGAich4Z00Q56JyEdUKQTkIk4VVQ058OEOB mhuKiebNy2Sw+qp8SIi6T8WI0YXeSD7d =yY5w Newsgroups: comp.std.c++ Tom Hahn writes: > Does anyone (hopefully someone from SGI) know about the company's > reaction to the November ISO FDIS on the subject of the STL string > class? > > Specifically, are they happy enough to implement it in the next > release, and if so when might that happen. Thanks. They already have a nearly conformant string class which works. It doesn't have sharing and copy on write. The intent of the commitee is to allow but not mandate sharing. The string class as defined in the London draft is usable (the CD2 one was strictly unusable). The problem is that sharing is often impossible as: - operator[] has to return a charT& - the reference is valid until you mutate the containner for ex. with append (not just its elements) so, as op[] is typically used often, often the sharing won't take place. So SGI will continue to provide a non sharing string class and 'rope'. Note: I am a student; I am not from SGI. -- Valentin Bonnard mailto:bonnardv@pratique.fr info about C++/a propos du C++: http://www.pratique.fr/~bonnardv/ --- [ comp.std.c++ is moderated. To submit articles: try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html ] [ Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ] [ Comments? mailto:std-c++-request@ncar.ucar.edu ]