gecko-dev/string/obsolete
jaggernaut%netscape.com 5a6317b8a5 Bug 88413: Remove |GetUnicode()| from nsString (and replace it with |get()|). r=dbaron, rs=scc.
This removes all call-sites I can currently fix. Tomorrow I'll try to get someone to checkin my changes to security/ and I'll get some help with the Netscape side of things.

nsString::GetUnicode()'s final death-blow will be dealt soon. Please keep this in mind as you add new code :-)
2001-06-30 11:02:25 +00:00
..
.cvsignore Adding and updating necessary .cvsignore files. Bug #61550 2001-02-24 06:22:49 +00:00
MANIFEST bug #74726: sr=waterson, r=beard. Make |nsXPIDLC?String| inherit from |nsSharableC?String|, the new implementation is now in the string hierarchy (and out of string/obsolete). 2001-06-29 12:47:43 +00:00
Makefile.in bug #74726: sr=waterson, r=beard. Make |nsXPIDLC?String| inherit from |nsSharableC?String|, the new implementation is now in the string hierarchy (and out of string/obsolete). 2001-06-29 12:47:43 +00:00
README.html fixing documentation 2001-03-08 04:47:24 +00:00
bufferRoutines.h bug #74726: sr=waterson, r=beard. Make |nsXPIDLC?String| inherit from |nsSharableC?String|, the new implementation is now in the string hierarchy (and out of string/obsolete). 2001-06-29 12:47:43 +00:00
makefile.win bug #74726: sr=waterson, r=beard. Make |nsXPIDLC?String| inherit from |nsSharableC?String|, the new implementation is now in the string hierarchy (and out of string/obsolete). 2001-06-29 12:47:43 +00:00
nsStr.cpp landing string branch; see bug #73786 2001-04-02 19:40:52 +00:00
nsStr.h bug #74726: sr=waterson, r=beard. Make |nsXPIDLC?String| inherit from |nsSharableC?String|, the new implementation is now in the string hierarchy (and out of string/obsolete). 2001-06-29 12:47:43 +00:00
nsString.cpp Bug 88413: Remove |GetUnicode()| from nsString (and replace it with |get()|). r=dbaron, rs=scc. 2001-06-30 11:02:25 +00:00
nsString.h Add hack to make functions that used to work with nsXPIDLString continue to work now that nsXPIDLString inherits from nsAString by adding inline methods to resolve ambiguity for compilers that don't support |explicit|. r=jaggernaut sr=waterson b=88411, 88420 2001-06-29 23:12:48 +00:00
nsString2.cpp bug #78658: checking in Chris Seawoods trivial fix to prevent writing to the console in optimized builds, sr=scc (myself) 2001-05-07 23:36:59 +00:00
nsString2.h Add hack to make functions that used to work with nsXPIDLString continue to work now that nsXPIDLString inherits from nsAString by adding inline methods to resolve ambiguity for compilers that don't support |explicit|. r=jaggernaut sr=waterson b=88411, 88420 2001-06-29 23:12:48 +00:00

README.html

<html>
<!-- 
   - The contents of this file are subject to the Mozilla Public
   - License Version 1.1 (the "License"); you may not use this file
   - except in compliance with the License. You may obtain a copy of
   - the License at http://www.mozilla.org/MPL/
   - 
   - Software distributed under the License is distributed on an "AS
   - IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
   - implied. See the License for the specific language governing
   - rights and limitations under the License.
   - 
   - The Original Code is Mozilla.
   - 
   - The Initial Developer of the Original Code is Netscape
   - Communications.  Portions created by Netscape Communications are
   - Copyright (C) 2001 by Netscape Communications.  All
   - Rights Reserved.
   - 
   - Contributor(s):
   -   Scott Collins <scc@mozilla.org> (original author)
  --> 
<body>
  <h1><span class="LXRSHORTDESC">original string implementations soon to be replaced (the names you are using will still be good)</span></h1>
<p>
  <span class="LXRLONGDESC">These are the original string implementations by rickg and others.
  Most of the code here will be made obsolete by the new shared-buffer string (see bug <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=53065">#53065</a>).
  For the most part, this change is intended to be transparent to clients.
  The type names you are using for strings now, e.g., nsString, nsAutoString, nsXPIDLString, will still be good,
    they will just refer to better, but compatible, implementations.
  If you're interested in learning how strings work, you probably want to start with
    <a href="http://lxr.mozilla.org/seamonkey/source/string/public/nsAReadableString.h">nsAReadableString</a>.</span>
</p>
</body>
</html>