From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: extern modifier on function declarations
Date: Thu, 08 Dec 2016 15:45:00 -0000 [thread overview]
Message-ID: <9c9c81880b49120bf90766fce93503ac@simark.ca> (raw)
Hi gdb-patches,
Our coding style currently requires using the "extern" keyword on
function declarations. How relevant is this today?
I am not good at reading standards, but it is my impression that in C++,
functions are always extern unless they are declared static. I am sure
some people here know that answer already.
If it's not useful anymore, I would suggest dropping it for future
patches. It doesn't change much, just a bit less verbosity and line
wrapping.
Simon
next reply other threads:[~2016-12-08 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 15:45 Simon Marchi [this message]
2016-12-09 9:23 ` Yao Qi
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=9c9c81880b49120bf90766fce93503ac@simark.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.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