From: "Christian Biesinger via gdb" <gdb@sourceware.org>
To: gdb@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Renaming .c files to .cc?
Date: Tue, 10 Dec 2019 22:19:00 -0000 [thread overview]
Message-ID: <CAPTJ0XEXR2Kb9CU1j17g9VE9fU07xsWHJSk4QiD1ma47F1TSsA@mail.gmail.com> (raw)
Hello all,
I was wondering what people's thoughts are on renaming the .c files to
.cc, since they are in fact C++ code? (Only for files under gdb/)
Advantages:
- Easier for newcomers to see that the code is, in fact, C++
- Editors will syntax highlight C++ keywords w/o having to be told
that these files are C++
On IRC it was mentioned that git may have issues with renames like
that but I have found that "git log --follow" and such are doing a
good job with that, at least as long as the same commit doesn't change
the file too much while it is renamed, which I wouldn't expect to be a
problem here.
Thoughts?
Christian
next reply other threads:[~2019-12-10 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 22:19 Christian Biesinger via gdb [this message]
2019-12-11 0:42 ` Luis Machado
2019-12-11 1:27 ` Christian Biesinger via gdb
2019-12-11 1:33 ` Luis Machado
2019-12-11 2:24 ` Simon Marchi
2019-12-11 3:32 ` Eli Zaretskii
2019-12-11 23:00 ` Christian Biesinger via gdb
2019-12-12 6:17 ` Eli Zaretskii
2019-12-14 18:20 ` Christian Biesinger via gdb
2019-12-11 10:59 ` Pedro Alves
2019-12-11 16:35 ` Eli Zaretskii
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=CAPTJ0XEXR2Kb9CU1j17g9VE9fU07xsWHJSk4QiD1ma47F1TSsA@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=cbiesinger@google.com \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).