home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!asuvax!ncar!vexcel!copper!slate!lpratt
- From: lpratt@slate.mines.colorado.edu (Lorien Pratt)
- Newsgroups: comp.lang.modula3
- Subject: Proper use of interfaces/modules for top-down programming?
- Message-ID: <1993Jan8.163340.12922@slate.mines.colorado.edu>
- Date: 8 Jan 93 16:33:40 GMT
- Sender: lpratt@slate.mines.colorado.edu (Lorien Pratt)
- Organization: Colorado School of Mines
- Lines: 26
-
- Hi,
- I wonder if somebody could answer some questions about, or give me a pointer
- to a reference for, how to do proper top-down programming with
- modula-3? I'm teaching this language for a data structures course and
- learning it at the same time, and I want to be sure I communicate
- whatever is the usual philosophy for modular coding in modula-3. I have
- the Harbison book, but chapter 8 seems to present more legal syntax than
- stylistic issues; and the programming conventions chapter doesn't get into
- modularity.
-
- For example, what's the proper way to go about developing a program?
- Do you write the Main module, then the interfaces, then try to compile to
- check for type consistency, then fill in the modules for the interfaces?
- Or do people typically write their interfaces and modules that export them,
- before trying to incorporate them into the main procedure? Is it a good
- idea to have multiple procedures per module?
-
- Thanks in advance for any help or pointers you can give!
- --Lori Pratt
-
-
- --
- L. Y. Pratt Dept. of Math and Computer Science
- lpratt@franklinite.mines.colorado.edu Colorado School of Mines
- (303) 273-3878 (work) 402 Stratton
- (303) 278-4552 (home) Golden, CO 80401, USA
-