From mboxrd@z Thu Jan  1 00:00:00 1970
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 <theymos@mm.st>) id 1RI51Q-0002cW-JH
	for bitcoin-development@lists.sourceforge.net;
	Sun, 23 Oct 2011 20:51:56 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of mm.st
	designates 66.111.4.29 as permitted sender)
	client-ip=66.111.4.29; envelope-from=theymos@mm.st;
	helo=out5.smtp.messagingengine.com; 
Received: from out5.smtp.messagingengine.com ([66.111.4.29])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1RI51P-00020v-IL
	for bitcoin-development@lists.sourceforge.net;
	Sun, 23 Oct 2011 20:51:56 +0000
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44])
	by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id DE6E1200DA
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 23 Oct 2011 16:51:49 -0400 (EDT)
Received: from web3.nyi.mail.srv.osa ([10.202.2.213])
	by compute4.internal (MEProxy); Sun, 23 Oct 2011 16:51:49 -0400
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
	id B944A821C88; Sun, 23 Oct 2011 16:51:49 -0400 (EDT)
Message-Id: <1319403109.18333.140660989434537@webmail.messagingengine.com>
X-Sasl-Enc: BkS15pNxjnNx0aVUMyaw214E+PwBagJY5uMC58NV8YH3 1319403109
From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
In-Reply-To: <CAJNQ0ssSQ0egHZ8YWFzrGv=LjfWQqV9V7qSeB01Zg2C4-LSZGQ@mail.gmail.com>
References: <CAMm66_=eqw9VqYrs5kv_i1di1FmDtP8X1dgBH90N0CuVvZswMA@mail.gmail.com><CA+s+GJBo90gH4pRx7+vnHgy5y6bWF7My69jNj6J-RHw7bBqH8g@mail.gmail.com>
	<CAJNQ0ssSQ0egHZ8YWFzrGv=LjfWQqV9V7qSeB01Zg2C4-LSZGQ@mail.gmail.com>
Date: Sun, 23 Oct 2011 15:51:49 -0500
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(theymos[at]mm.st)
	-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
	0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1RI51P-00020v-IL
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: Sun, 23 Oct 2011 20:51:56 -0000

It's legal for a scope to define variables with names that conflict with
the names of variables in higher-level scopes.