public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Vance <briareos@lokigames.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gcc@gcc.gnu.org
Subject: Re: list<>.size()
Date: Fri, 31 Mar 2000 17:34:00 -0000	[thread overview]
Message-ID: <20000331173410.D807@namaste.lokigames-lan.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003311703470.14988-100000@propylaea.anduin.com>

On Fri, Mar 31, 2000 at 05:05:49PM -0800, Daniel Berlin wrote:

> AFAICT, no.

Bummer.

> Looking at the STL docs, I don't see size guaranteed to be O(1).

No, it is not mandated.

> guaranteed to be O(1) in complexity, i would strongly encourage your
> programs to stop assuming it is.

I port code for a living. I have no control over the original
developer's intelligence. But it seems this thing wouild be trivial to
implement and rectify an important porting issue. Changing every

while( list<>.size( ) ) {
       iterator is = list.begin( );
       delete *is;
       list<>.erase( is );
}

is tedious. As is changing every:

if( list<>.size( ) ) {
    // do blah
}

m.

-- 
Programmer             "Ha ha." "Ha ha." "What are you laughing at?"
Loki Software                      "Just the horror of being alive."
http://lokigames.com/~briareos/                   - Tony Millionaire

  reply	other threads:[~2000-03-31 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-31 16:33 list<>.size() Michael Vance
2000-03-31 17:08 ` list<>.size() Daniel Berlin
2000-03-31 17:34   ` Michael Vance [this message]
2000-03-31 17:46     ` list<>.size() Tudor Hulubei
2000-03-31 18:08       ` list<>.size() Michael Vance
     [not found]         ` <d97lei1oh1.fsf@han.cs.umn.edu>
2000-03-31 19:46           ` list<>.size() Michael Vance
2000-04-01  1:46         ` list<>.size() llewelly
2000-03-31 18:01     ` list<>.size() Joe Buck
2000-03-31 18:11       ` list<>.size() Michael Vance
2000-04-03  9:05         ` list<>.size() Joe Buck
2000-04-03 13:36           ` list<>.size() Ross Smith
2000-03-31 20:09 ` list<>.size() Dima Volodin

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=20000331173410.D807@namaste.lokigames-lan.com \
    --to=briareos@lokigames.com \
    --cc=dan@cgsoftware.com \
    --cc=gcc@gcc.gnu.org \
    /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).