Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of speakeasy.net
	designates 69.17.117.49 as permitted sender)
	client-ip=69.17.117.49; envelope-from=agrimes@speakeasy.net;
	helo=mail5.sea5.speakeasy.net; 
Message-ID: <4E1BC9D0.3080104@speakeasy.net>
Date: Tue, 12 Jul 2011 00:13:04 -0400
From: Alan Grimes <agrimes@speakeasy.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:5.0) Gecko/20110711 Firefox/5.0 SeaMonkey/2.2
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <97305540.4426247.1310337435268.JavaMail.fmail@mwmweb052>
	<201107102201.53937.luke@dashjr.org>
In-Reply-To: <201107102201.53937.luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] overall bitcoin client code quality
Precedence: list

Yeah, I'm starting to run into real design problems in my attempt to 
write a bitcoin daemon, namely I'm trying to figure out how to manage 
connections and peers and how to interpret and coordinate messages from 
peers.

While spying on the old code, I noticed one major problem that could be 
fixed quite easily. That is, the 1 class-per .h/.cpp rule is completely 
ignored in main.h/cpp and net.h/cpp If all of the classes in the project 
were re-factored to their own files, it would be much easier to audit 
what was interacting with what. I think this work could be done within 
16 programmer hours.

The old codebase doesn't build on my system but I'd be willing to rough 
it in anyway.

I think this should be done in parallel to efforts, such as mine, to 
re-implement major functionality.

-- 
E T F
N H E
D E D

Powers are not rights.