From 4608164832395548478 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,cc1a555bbe9617a3 X-Google-Attributes: gidf78e5,public From: Pete Becker Subject: Re: STL and SGI and strings Date: 1998/01/13 Message-ID: <34BAA6FB.17121A3E@acm.org>#1/1 X-Deja-AN: 315554480 Content-Transfer-Encoding: 7bit References: <34B57837.41C6@pixar.com> <34B6580F.6A50@pratique.fr> X-Original-Date: Mon, 12 Jan 1998 18:27:55 -0500 Content-Type: text/plain; charset=us-ascii Organization: MediaOne -=- Northeast Region X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBFAgUANLuFM+EDnX0m9pzZAQHC/gF+NUC99+NbhaPCEvahqfZaorfghdeRjDWt kgdKHKxeNxwiAI4RqS9QTlRF/mP6D+wf =e7Z0 Mime-Version: 1.0 Newsgroups: comp.std.c++ J. Kanze wrote: > > > In my own code, I don't think I've > ever used an op[], either in my own string class or someone elses. I'll > admit that I cheat, however -- when parsing, I normally do the > equivalent of c_str(), and use the resulting pointer:-). That's not cheating. I was against having operator[] in the string class at all, but the forces of inertia were impossible to overcome. -- Pete --- [ 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 ]