public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9894: sscanf %d doesn't work with short data type
Date: Wed, 05 Mar 2003 20:46:00 -0000 [thread overview]
Message-ID: <20030305204601.30411.qmail@sources.redhat.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
The following reply was made to PR c/9894; it has been noted by GNATS.
From: Andreas Schwab <schwab@suse.de>
To: "Park JongAm" <jongampark@hotmail.com>
Cc: cgf@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c/9894: sscanf %d doesn't work with short data type
Date: Wed, 05 Mar 2003 21:43:10 +0100
"Park JongAm" <jongampark@hotmail.com> writes:
|> Maybe it's not a "bug" of the gcc. However it doesn't work like other
|> compilers, and that can make people confused.
It's not a compiler issue. You are invoking undefined behaviour. Don't
do that.
|> Wouldn't it be better to display error message, "Type not compatible",
|> etc?
-Wformat -Werror
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2003-03-05 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 20:46 Andreas Schwab [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 20:06 Park JongAm
2003-03-01 7:28 cgf
2003-03-01 1:56 jongampark
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=20030305204601.30411.qmail@sources.redhat.com \
--to=schwab@suse.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).