From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Local type inference with auto is in C2X
Date: Thu, 3 Nov 2022 18:04:31 +0000 [thread overview]
Message-ID: <3f573e-a863-e1e6-f5be-83a6d7d32da0@codesourcery.com> (raw)
In-Reply-To: <87zgd8fhn4.fsf@oldenburg.str.redhat.com>
On Thu, 3 Nov 2022, Florian Weimer via Gcc wrote:
> My main worry is that both Clang and GCC still enable implicit ints by
> default. This means that auto variables have type int always, and that
> can subtly alter the meaning of programs. The only indication that this
> has happened in a code base is a warning that went away (!). I don't
> like that.
My expectation is that the old use of auto as a storage class specifier is
actually very rare in C code, so this particular sub-case (auto with no
type specifier meaning implicit int) is even rarer and there isn't much
porting to be done for it (unlike for the rest of implicit int).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-11-03 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 10:37 Florian Weimer
2022-11-03 15:19 ` Michael Matz
2022-11-04 14:16 ` David Brown
2022-11-03 18:04 ` Joseph Myers [this message]
2022-11-03 18:33 ` Florian Weimer
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=3f573e-a863-e1e6-f5be-83a6d7d32da0@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.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).