From: Gavin Kistner <gavin@...>
Date: 2005-07-12T14:03:10+09:00
Subject: Re: Splitting source code

--Apple-Mail-4--1044021463
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

On Jul 11, 2005, at 10:29 PM, Austin Ziegler wrote:
> I find it very rare to find that a single class is
> defined over multiple files, except in the possible case of a C
> extension.

FWIW, I did this something like this with my ValidForm library. A  
single file defined a base set of functionality for many classes, and  
then a second file could optionally be included that added a custom  
#to_html method to every one of those classes.

If I had to do it again, I might have subclassed all the originals in  
a separate file...but then again I might not have.

It feels sketchy-but-acceptable to me to have FileB require FileA to  
be meaningful, as long as FileA can stand on its own. It feels  
pointless to me to have FileA and FileB mutually require each other  
to be useful, for if that's the case, why not have them as one file?

--Apple-Mail-4--1044021463--