1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1UqTUe-0008Im-AS
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Jun 2013 19:29:04 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.42 as permitted sender)
client-ip=74.125.82.42; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f42.google.com;
Received: from mail-wg0-f42.google.com ([74.125.82.42])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UqTUa-0007p5-TO
for bitcoin-development@lists.sourceforge.net;
Sat, 22 Jun 2013 19:29:04 +0000
Received: by mail-wg0-f42.google.com with SMTP id z11so1453606wgg.1
for <bitcoin-development@lists.sourceforge.net>;
Sat, 22 Jun 2013 12:28:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type
:x-gm-message-state;
bh=wNeEpOZqq3BRDrnThKFWh/0b6VrOcZOeTvt8p5hdbhg=;
b=HH9oGjNrW3h+HG+5/eYW3mNKK3ugxoT5OvyAtwkMmWNwXJKKakkbiYV0WiDtgspteL
ESjn4eyTILyAKNiHdV4KFVVU3zxDXrO3l97k24wmIKc0AUTY6GtWUO8o138ocsfipEA8
cWQ5ndNVJe0x5FnIO8PB0cW1a04+qOORHAuwiR3+IYPjAmRPBTr+zD8cFBZ8/OtWAFie
JNihuv3QWO14N7pgWGSP/kHYFakSAENIj7+i7zuEip74Mf3UkQRLmoKWLRNZwIW/Hg+e
/YLh4sBCyznQxhfXduCXr0sJFfbYfE2QZovUHxq1a1vPhf9QgT/+57gASEAmZt9fIYxq
i9Bw==
MIME-Version: 1.0
X-Received: by 10.194.90.244 with SMTP id bz20mr12942052wjb.69.1371929334468;
Sat, 22 Jun 2013 12:28:54 -0700 (PDT)
Received: by 10.194.178.69 with HTTP; Sat, 22 Jun 2013 12:28:54 -0700 (PDT)
Date: Sat, 22 Jun 2013 15:28:54 -0400
Message-ID: <CAJHLa0Mu+1jB8gPbzH3JTXk0uWTJiZOfogffj6+nUfekOgN-0A@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQn6UVpXit8wlMJSEIpMyJiCW/Lj3ovMJwEvQ3l2FBHgvwFjVWxPApjULRgin/Q+A51Q5sG+
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UqTUa-0007p5-TO
Subject: [Bitcoin-development] bitcoind and C++ namespaces?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2013 19:29:04 -0000
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/
|
