public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: aj@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9569: 8 bytes seems to long for long long int Date: Thu, 06 Feb 2003 00:16:00 -0000 [thread overview] Message-ID: <20030206001601.6969.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9569; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> Cc: Neil Booth <neil@daikokuya.co.uk>, <aj@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <stefaandr@hotmail.com>, <gcc-gnats@gcc.gnu.org> Subject: Re: c/9569: 8 bytes seems to long for long long int Date: Thu, 6 Feb 2003 00:06:25 +0000 (GMT) On 6 Feb 2003, Falk Hueffner wrote: > I still don't get it. In C99, this is perfectly legal code, and does > what the reporter wants. It is of course documented nowhere, but I > would assume that g++ inherits C99's long long semantics if long long > is enabled. Why not this part? C++98 is stricter than C90 about integer constants. _Explicitly_ using long long is one thing (accepted as an extension by the C++ compiler), _implicitly_ using it (by having too large an integer constant without a suffix) is another. The behaviour may or may not be as intended; that's for the C++ maintainers to work out. -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2003-02-06 0:16 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-06 0:16 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-06 7:36 Segher Boessenkool 2003-02-06 7:06 Neil Booth 2003-02-06 0:06 Falk Hueffner 2003-02-05 23:46 Neil Booth 2003-02-05 22:56 Joseph S. Myers 2003-02-05 21:06 Neil Booth 2003-02-04 18:36 Falk Hueffner 2003-02-04 14:37 aj 2003-02-04 14:36 Andreas Jaeger 2003-02-04 13:36 stefaandr
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=20030206001601.6969.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --cc=aj@gcc.gnu.org \ --cc=gcc-prs@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: linkBe 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).