From: Dodji Seketeli <dodji@redhat.com>
To: libabigail@sourceware.org
Subject: Moving the code base to C++11
Date: Thu, 03 Dec 2020 15:44:02 +0100 [thread overview]
Message-ID: <87blfb2bm5.fsf@redhat.com> (raw)
Hello,
As of patch https://sourceware.org/pipermail/libabigail/2020q4/002976.html, we
can now write C++11 code in the project :-)
That patch updated the CONTRIBUTING file in the source tree to state
that and to give some very basic guidelines.
I haven't written any specific coding convention and I don't think we
need one right now. Or do we?
I think we can just use our judgement here and use features that make
the source code more pleasant to read while keeping or even increasing
type safety.
As much as possible, I would find it preferable to keep the code base
consistent with the current indentation and formatting practises as we
see it fit.
Other than that, I hope you'll enjoy moving into C++11 territory which
I hope will bring progress to our programming and more importantly
debugging and maintenance experience.
Cheers,
--
Dodji
reply other threads:[~2020-12-03 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87blfb2bm5.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=libabigail@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).