public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: kunert@physik.tu-dresden.de (Thomas Kunert)
Cc: egcs@cygnus.com
Subject: Re: New STL implementation from SGI
Date: Mon, 13 Jul 1998 15:28:00 -0000	[thread overview]
Message-ID: <199807132206.PAA27063@atrus.synopsys.com> (raw)
In-Reply-To: <35AA1A97.5B38BBF2@physik.tu-dresden.de>

> What is the purpose of reference-counted strings?

In many applications, they are reasonably fast.

> For portable code, one cannot depend on fast copy-operations ...

meaning that if egcs uses a reference-counted string class, people moving
from a class that works like Microsoft CString (always deep copy) will
see a speedup.  In practice, since the committee said nothing about speed,
people who need speed can't use the standard string class at all; they
would need to design a custom class or else specifically choose which
class to use on a per-platform basis.

> and if one writes code especially for egcs, rope is better anyway.

Not always.  For many operations where the current egcs string, or the SGI
string, are O(1), rope is O(log(N)).  See the SGI documentation on rope
for a discussion.  Some rope operations are slow.  But rope will run on
many compilers, not just egcs, so using rope isn't that unportable.



  reply	other threads:[~1998-07-13 15:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-13  1:48 Ross Smith
1998-07-13  8:40 ` Thomas Kunert
1998-07-13 15:28   ` Joe Buck [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-13 17:29 Mike Stump
1998-07-14  8:41 ` Joe Buck
1998-07-13 17:29 Mike Stump
1998-07-11  6:31 Josh Stern
1998-07-07 22:54 Josh Stern
     [not found] <x7sokk1h55.fsf.cygnus.egcs@peti.gmd.de>
1998-07-02 15:15 ` Nathan Myers
1998-07-03 12:21   ` Andi Kleen
1998-07-05 15:40     ` Martin von Loewis
     [not found] ` <k2d8bm4x5k.fsf.cygnus.egcs@zero.aec.at>
1998-07-05 19:46   ` Nathan Myers
1998-07-08  3:16     ` Gerald Pfeifer
1998-07-08 16:34       ` Branko Cibej
1998-07-02  7:08 Peter Simons
1998-07-06  4:08 ` Jeffrey A Law
1998-07-06  8:09   ` H.J. Lu
1998-07-06 14:48     ` Jeffrey A Law
1998-07-06 22:11       ` Ben Scherrey
1998-07-07  0:14         ` Jeffrey A Law
     [not found]         ` <6669.899795405.cygnus.egcs@hurl.cygnus.com>
1998-07-08 16:34           ` Nathan Myers
1998-07-06 18:52     ` Alex Buell
1998-07-07  5:29       ` Carlo Wood
1998-07-07 10:14         ` B. James Phillippe
1998-07-07 12:51         ` Martin von Loewis
1998-07-07 22:54           ` H.J. Lu
1998-07-08  9:58           ` Joe Buck
     [not found]           ` <199807081547.IAA06604.cygnus.egcs@atrus.synopsys.com>
1998-07-09 11:18             ` Ulrich Drepper
1998-07-09 17:02               ` Joe Buck
1998-07-09 17:40                 ` Ulrich Drepper
1998-07-10  6:04                 ` Pieter Nagel
1998-07-10 13:32                   ` Joe Buck
     [not found]                 ` <Pine.LNX.3.96.980710103559.18309h-100000.cygnus.egcs@basilisk>
1998-07-10 20:04                   ` Nathan Myers
     [not found]               ` <199807100002.RAA10346.cygnus.egcs@atrus.synopsys.com>
1998-07-10 16:49                 ` Nathan Myers
1998-07-07  1:12     ` Joe Buck
1998-07-06 18:10       ` H.J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199807132206.PAA27063@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=egcs@cygnus.com \
    --cc=kunert@physik.tu-dresden.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).