From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>,
Nathan Sidwell <nathan@codesourcery.com>
Subject: Re: Do C++ signed types have modulo semantics?
Date: Tue, 28 Jun 2005 17:58:00 -0000 [thread overview]
Message-ID: <m37jgeictf.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0506281643440.12318@digraph.polyomino.org.uk>
"Joseph S. Myers" <joseph@codesourcery.com> writes:
| On Tue, 28 Jun 2005, Gabriel Dos Reis wrote:
|
| > Yes, we should document this. In general, implementation defined
| > aspects (and some of the undefined behaviour aspects) are missing
| > documentation for C++ -- JSM did some work for that for C.
|
| Is there a convenient checklist for C++ similar to C99's Annex J.3 and
| J.4, or is it necessary to go through the whole standard to find what
| needs documenting?
There is no such things as the C99's annex for C++. So, I'm afraid
one would go through the entire document. I'll raise the issue so
that the next C++0x has something similar. But, int the meantime, I'd
try to produce a collection based on grep.
-- Gaby
next prev parent reply other threads:[~2005-06-28 17:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF0E4366CA.5D54868B-ON4325702E.0036D351-4325702E.003973C5@il.ibm.com>
[not found] ` <m3k6keeibo.fsf@uniton.integrable-solutions.net>
2005-06-28 13:29 ` Nathan Sidwell
2005-06-28 13:59 ` Gabriel Dos Reis
2005-06-28 14:05 ` Andrew Pinski
2005-06-28 14:13 ` Gabriel Dos Reis
2005-06-28 15:30 ` Michael Veksler
2005-06-28 15:49 ` Nathan Sidwell
2005-06-28 15:58 ` Michael Veksler
2005-06-28 16:07 ` Andrew Pinski
2005-06-28 16:39 ` Gabriel Dos Reis
2005-06-28 15:55 ` Gabriel Dos Reis
2005-06-28 16:47 ` Joseph S. Myers
2005-06-28 17:58 ` Gabriel Dos Reis [this message]
2005-06-28 14:05 ` Nathan Sidwell
2005-06-27 14:39 Morten Welinder
2005-06-27 15:21 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 5:09 Michael Veksler
2005-06-27 13:02 ` Nathan Sidwell
2005-06-27 14:10 ` Gabriel Dos Reis
2005-06-27 14:36 ` Nathan Sidwell
2005-06-27 14:47 ` Paul Koning
2005-06-27 15:21 ` Michael Veksler
2005-06-28 3:06 ` Mark Mitchell
2005-06-28 3:49 ` Gabriel Dos Reis
2005-06-28 10:08 ` Robert Dewar
2005-06-28 11:19 ` Steven Bosscher
2005-06-28 12:03 ` Ulrich Weigand
2005-06-28 12:09 ` Steven Bosscher
2005-06-29 16:46 ` Steven Bosscher
2005-06-29 18:01 ` Daniel Berlin
2005-06-29 18:32 ` Steven Bosscher
2005-06-29 18:45 ` Robert Dewar
2005-06-29 19:13 ` Nicholas Nethercote
2005-06-28 12:16 ` Paul Koning
2005-06-28 12:30 ` Steven Bosscher
2005-06-28 12:35 ` Michael Veksler
2005-06-28 12:38 ` Steven Bosscher
2005-06-28 16:54 ` Joe Buck
2005-06-28 17:02 ` Mark Mitchell
2005-06-28 17:08 ` Daniel Berlin
2005-06-28 18:12 ` Mark Mitchell
2005-06-28 17:46 ` Theodore Papadopoulo
2005-06-27 15:17 ` Gabriel Dos Reis
2005-06-30 20:53 ` Kai Henningsen
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=m37jgeictf.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=nathan@codesourcery.com \
/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).