From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: "Martin Liška" <mliska@suse.cz>, "Toon Moene" <toon@moene.org>,
"Martin Jambor" <mjambor@suse.cz>,
"GCC Mailing List" <gcc@gcc.gnu.org>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Mass rename of C++ .c files to .cc suffix
Date: Tue, 11 Jan 2022 18:23:51 +0000 [thread overview]
Message-ID: <CAH6eHdSjdwaft_-Jci0pfXCJeDduc8cbMepGdzEUAc+dOAudwg@mail.gmail.com> (raw)
In-Reply-To: <e9d20c6e-9485-2655-64ca-d4c46e0b23b8@gmx.de>
On Tue, 11 Jan 2022 at 18:02, Harald Anlauf via Gcc <gcc@gcc.gnu.org> wrote:
>
> Am 11.01.22 um 16:50 schrieb Martin Liška:
> > On 1/11/22 16:48, Toon Moene wrote:
> >> On 1/11/22 13:56, Martin Liška wrote:
> >>
> >>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
> >>> Plus it survives build of all FEs (--enable-languages=all) on
> >>> x86_64-linux-gnu
> >>> and I've built all cross compilers.
> >>
> >> Does this also rename .c files in the fortran and libgfortran
> >> directories ?
> >
> > Hello.
> >
> > Yes, it does the first one.
>
> Regarding fortran: can we have a vote on this one?
>
> Some developers (including myself) are not really familiar with C++,
> and in the past preference has been expressed on the fortran ML in
> favor of not using too much C++.
>
> I would also not really be in a position to review real C++ code.
The discussion is purely about renaming files that are *already* C++
source files but have the misleading .c file extension.
Nobody is suggesting using C++ where it isn't already being used.
next prev parent reply other threads:[~2022-01-11 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ri6mtk7vo41.fsf@suse.cz>
[not found] ` <57564370-7184-ef62-039e-60b150058fd8@suse.cz>
[not found] ` <68946bf6-4b2f-b8f3-20b3-5cf3f2fd611c@moene.org>
2022-01-11 15:50 ` Martin Liška
2022-01-11 15:56 ` Jakub Jelinek
2022-01-11 16:03 ` Martin Liška
2022-01-11 16:16 ` Jakub Jelinek
2022-01-12 8:58 ` Martin Liška
2022-01-12 15:54 ` [PATCH] git-backport: support renamed .cc files in commit message Martin Liška
2022-01-14 7:44 ` Bernhard Reutner-Fischer
2022-01-14 15:26 ` Martin Liška
2022-01-17 21:26 ` Martin Liška
2022-01-18 19:10 ` Harald Anlauf
2022-01-18 19:10 ` Harald Anlauf
2022-01-19 8:07 ` Martin Liška
2022-01-11 18:00 ` [PATCH] Mass rename of C++ .c files to .cc suffix Harald Anlauf
2022-01-11 18:00 ` Harald Anlauf
2022-01-11 18:23 ` Jonathan Wakely [this message]
2022-01-11 18:36 ` Jakub Jelinek
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=CAH6eHdSjdwaft_-Jci0pfXCJeDduc8cbMepGdzEUAc+dOAudwg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
--cc=toon@moene.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).