Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!ENG.SUN.COM!Mitch.Bradley
From: Mitch.Bradley@ENG.SUN.COM
Newsgroups: comp.lang.forth
Subject: Modular coding style
Message-ID: <9105210325.AA09766@ucbvax.Berkeley.EDU>
Date: 21 May 91 02:57:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Mitch.Bradley%ENG.SUN.COM@SCFVM.GSFC.NASA.GOV
Organization: The Internet
Lines: 14

> Ray Duncan writes:
> In our larger programs, we make heavy use of the module concept, using a
> lot of little files which each contain a functional subset of the source
> code, and a "master" application file which holds the definitions of global
> variables and a bunch of "include" statements for the other files.  This
> approach seems to work well for us and also places pressure on us to
> keep the interfaces between the modules small and clean.

At Sun, we use the same style (lots of small files) for the Open Boot
firmware.  We use Unix source control and archival tools to help us
maintain the integrity of the source base in the face of lots of
programmers working on the same programs.

Mitch.Bradley@Eng.Sun.COM