Path: utzoo!mnetor!uunet!husc6!linus!philabs!gcm!dc
From: dc@gcm (Dave Caswell)
Newsgroups: comp.software-eng
Subject: Re: Question Re: Configuration Management
Message-ID: <411@white.gcm>
Date: 21 Feb 88 17:02:49 GMT
References: <497@aimt.UUCP> <24502@cca.CCA.COM> <1356@vaxb.calgary.UUCP>
Reply-To: dc@white.UUCP (Dave Caswell)
Organization: Greenwich Capital Markets, Greenwich, CT
Lines: 13
Keywords: configuration management, software design

=The basic problem with keeping several procedures in one physical file
=is that it becomes more difficult (both conceptually and physically) to
=manipulate individual procedures.  If you know that you never have
=to treat a particular procedure as an individual unit, then placing
=a group in one file makes more sense (eg, as with Hash_get, Hash_put, etc).
=
The computer system we just finished is 73,000 lines.  It is in 128 source
files and has 1874 functions.  I couldn't imagine the complexity of having
1874 separate files.   How could a person possibly tell what is related to 
what?   Each file reads from top to bottom like a book.  We weren't at all
concerned with time to load the editor.    The project took 3 people-years
or over 250,000$.    The time was spent debugging, designing, and learning
the application.  It wasn't spent waiting for emacs to startup.