From: wsdngtmp@... (Sascha Doerdelmann)
Date: 2004-05-06T16:53:56+09:00
Subject: Re: One class per file

Jim Freeze <jim@freeze.org> wrote:
> We base this decision on reuse.

My favourite answer.

I find myself making new files whenever I notice pieces of code I'd
like to use in different applications.

But what's the best way to organize those files? Groups of files
naturally belong to directories. Using a single folder per application
works fine if I don't reuse files. One day I will come to the point
where I have to maintain reusable files in different directories. The
next step will be that wo different applications need different
versions of the files and as far as I can see neither cvs nor
subversion help me with this kind of problem.

I am sure that the Ruby community will find appropriate anwers to
different kind of code reuse problems. As I am coding VisualWorks
Smalltalk most of the time, I like the idea of managing code rather
than files. The current Ruby way has the advantage that there is no
special build procedure and you can distribute applications by just
distributing their sources.

Cheers
Sascha