public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/31370] resizing bugs in std::vector<bool>
Date: Tue, 27 Mar 2007 20:03:00 -0000	[thread overview]
Message-ID: <20070327200305.29976.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31370-14320@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from pcarlini at suse dot de  2007-03-27 21:03 -------
Two quick replies:

> 4.2 doesn't fix any of the problems, but it does make the max_size
> issue a bit more confusing.

Thanks, this is encouraging ;) In any case, nobody said 4.2 fixed any of those
problems. However, for sure, any proposed patch / fix targets first mainline,
not the release branches.

> Note that it probably isn't correct to assume that difference_type is
> a ssize_t, and therefore has maximum SSIZE_MAX, but I don't see what
> the correct way to ask what the maximum value representable by
> difference_type is.

Why not numeric_limits<difference_type>::max() ?

> I'm fine with filling out copyright assignment paperwork, but I didn't see the
> form at the link you gave me.

Again, nobody said the form was there. I pointed you at that general
information page because I was under the - probably not too far from the truth
- impression that you was not familiar with our general directions for
contributors. If you need the forms, please send a message to assignments@.

In any case, that kind of paperwork is not needed for the present work, but, if
possible, please let's figure out a way to deal with the issues in a "C++"
(C++03, actually) way, which means using numeric_limits, not assuming specific
types for difference_type, size_type and so on, not using types likes ssize_t
which do not exist in the current C++ standard (*). Finally, I repeat myself,
any patch shall target mainline first.

I look forward to see your improved proposal.

(*) ssize_t is mentioned only once, in note 266. If we really need a type
equivalent for all practical matters to such Posix type, we have to find a way
to construct one on the fly, for example by implementing an __add_signed
(similar to the currently available __add_unsigned, in ext/type_traits.h) 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31370


  parent reply	other threads:[~2007-03-27 20:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27  3:03 [Bug libstdc++/31370] New: resizing bugs in std::vector gcc at severeweblint dot org
2007-03-27  3:09 ` [Bug libstdc++/31370] " gcc at severeweblint dot org
2007-03-27  3:20 ` gcc at severeweblint dot org
2007-03-27  6:05 ` [Bug libstdc++/31370] resizing bugs in std::vector<bool> pinskia at gcc dot gnu dot org
2007-03-27  7:52 ` fang at csl dot cornell dot edu
2007-03-27  8:07 ` pcarlini at suse dot de
2007-03-27 19:27 ` gcc at severeweblint dot org
2007-03-27 20:03 ` pcarlini at suse dot de [this message]
2007-03-31 16:52 ` pcarlini at suse dot de
2007-04-02 10:16 ` paolo at gcc dot gnu dot org
2007-04-02 10:19 ` pcarlini at suse dot de

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=20070327200305.29976.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).