From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: Replace operator new / operator new[]
Date: Fri, 23 Sep 2016 19:53:00 -0000 [thread overview]
Message-ID: <20160923193612.GG3842@adacore.com> (raw)
In-Reply-To: <CAH=s-PNoCqScXAhZ+t44ybgvE1ZkHZV1OPk6Hi19Muz78kEmQg@mail.gmail.com>
> To be clear, I didn't suggest renaming all .c files to .cc files. In case
> that we add a new file, I wonder we may name it .cc.
>
> If mixed .c and .cc is confusing, I am fine with cpp files with .c suffix.
I think it's best to stay with .c for practical reasons. Otherwise,
the massive rename is going to create one "interesting" challenge
for everyone who's maintaining a set a patches they haven't/couldn't
contribute... Since the benefit is fairly minimal, it doesn't seem
to justify the cost, IMO.
--
Joel
prev parent reply other threads:[~2016-09-23 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 13:39 Pedro Alves
2016-09-23 9:49 ` Yao Qi
2016-09-23 16:14 ` Pedro Alves
2016-09-23 16:37 ` Yao Qi
2016-09-23 19:53 ` Joel Brobecker [this message]
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=20160923193612.GG3842@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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