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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
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 <witchspace81@gmail.com>) id 1RICgH-00083U-6P
for bitcoin-development@lists.sourceforge.net;
Mon, 24 Oct 2011 05:02:37 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.175 as permitted sender)
client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com;
helo=mail-yx0-f175.google.com;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1RICgF-0007uK-Ur
for bitcoin-development@lists.sourceforge.net;
Mon, 24 Oct 2011 05:02:37 +0000
Received: by yxi13 with SMTP id 13so1222959yxi.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 23 Oct 2011 22:02:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.77.164 with SMTP id t4mr2930763obw.9.1319432550559; Sun,
23 Oct 2011 22:02:30 -0700 (PDT)
Received: by 10.182.34.226 with HTTP; Sun, 23 Oct 2011 22:02:30 -0700 (PDT)
In-Reply-To: <1319403109.18333.140660989434537@webmail.messagingengine.com>
References: <CAMm66_=eqw9VqYrs5kv_i1di1FmDtP8X1dgBH90N0CuVvZswMA@mail.gmail.com>
<CA+s+GJBo90gH4pRx7+vnHgy5y6bWF7My69jNj6J-RHw7bBqH8g@mail.gmail.com>
<CAJNQ0ssSQ0egHZ8YWFzrGv=LjfWQqV9V7qSeB01Zg2C4-LSZGQ@mail.gmail.com>
<1319403109.18333.140660989434537@webmail.messagingengine.com>
Date: Mon, 24 Oct 2011 07:02:30 +0200
Message-ID: <CAJNQ0st7H9N-WDx-5R7JxKndPVXDEqTVvr6C20zZJv1UgvnZgg@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: theymos <theymos@mm.st>
Content-Type: multipart/alternative; boundary=f46d044401627b310b04b0045487
X-Spam-Score: -0.5 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1RICgF-0007uK-Ur
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Fwd: bitcoin scope issue in main.cpp
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: Mon, 24 Oct 2011 05:02:37 -0000
--f46d044401627b310b04b0045487
Content-Type: text/plain; charset=ISO-8859-1
Yes, I know that. It compiles.
If we pulled all the 'This is legal in C++' tricks in the bitcoin source it
would be even less maintainable and readable than now. But whatever...
JS
On Sun, Oct 23, 2011 at 10:51 PM, theymos <theymos@mm.st> wrote:
> It's legal for a scope to define variables with names that conflict with
> the names of variables in higher-level scopes.
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--f46d044401627b310b04b0045487
Content-Type: text/html; charset=ISO-8859-1
<br>Yes, I know that. It compiles.<br><br>If we pulled all the 'This is legal in C++' tricks in the bitcoin source it would be even less maintainable and readable than now. But whatever...<br><br>JS<br><br><div class="gmail_quote">
On Sun, Oct 23, 2011 at 10:51 PM, theymos <span dir="ltr"><<a href="mailto:theymos@mm.st">theymos@mm.st</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It's legal for a scope to define variables with names that conflict with<br>
the names of variables in higher-level scopes.<br>
<br>
------------------------------------------------------------------------------<br>
The demand for IT networking professionals continues to grow, and the<br>
demand for specialized networking skills is growing even more rapidly.<br>
Take a complimentary Learning@Cisco Self-Assessment and learn<br>
about Cisco certifications, training, and career opportunities.<br>
<a href="http://p.sf.net/sfu/cisco-dev2dev" target="_blank">http://p.sf.net/sfu/cisco-dev2dev</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</blockquote></div><br>
--f46d044401627b310b04b0045487--
|
