From: Keir Fraser <keir@xen.org>
To: Thanos Makatos <thanos.makatos@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: blktap3 in C++?
Date: Fri, 07 Sep 2012 16:21:44 +0100 [thread overview]
Message-ID: <CC6FCF98.4AF76%keir@xen.org> (raw)
In-Reply-To: <4B45B535F7F6BE4CB1C044ED5115CDDE011A6DAD77DF@LONPMAILBOX01.citrite.net>
On 07/09/2012 16:08, "Thanos Makatos" <thanos.makatos@citrix.com> wrote:
> I was wondering whether it would make sense to have blktap3 in C++. I don't
> have very strong feelings about it; I'd prefer to have it in C++, but it's
> already written in C and it works. The benefits of having it in C++ would be
> code clarity and maintainability. I bring this up now because I'm currently
> cleaning it up, so it's the best time to do it, should we decide to do so.
Leave it be, and learn how to write maintainable C code!
> --
> Thanos Makatos
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-09-07 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 15:08 blktap3 in C++? Thanos Makatos
2012-09-07 15:21 ` Keir Fraser [this message]
2012-09-07 21:08 ` Joseph Glanville
2012-09-10 8:38 ` Thanos Makatos
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=CC6FCF98.4AF76%keir@xen.org \
--to=keir@xen.org \
--cc=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xensource.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 NNTP newsgroup(s).