From: Jeff Garzik <jgarzik@bitpay.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] bitcoind and C++ namespaces?
Date: Sat, 22 Jun 2013 15:28:54 -0400 [thread overview]
Message-ID: <CAJHLa0Mu+1jB8gPbzH3JTXk0uWTJiZOfogffj6+nUfekOgN-0A@mail.gmail.com> (raw)
Slowly warming to C++ namespaces. How about starting small, and
wrapping most stuff inside a bitcoin namespace? Bike shedding can be
done at any point; the main idea is to start small, and gain
experience.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
reply other threads:[~2013-06-22 19:29 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=CAJHLa0Mu+1jB8gPbzH3JTXk0uWTJiZOfogffj6+nUfekOgN-0A@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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