Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!ut-sally!utah-cs!utah-orion!shebs
From: shebs@utah-orion.UUCP
Newsgroups: comp.lang.lisp
Subject: CL Packages
Message-ID: <154@utah-orion.UUCP>
Date: Sun, 29-Mar-87 17:54:36 EST
Article-I.D.: utah-ori.154
Posted: Sun Mar 29 17:54:36 1987
Date-Received: Tue, 31-Mar-87 00:47:39 EST
Organization: PASS Research Group
Lines: 14

My practice (with which many people will disagree) is to leave off the
package stuff until very late in development.  I know that some programmers
start a file by deciding on a package, exports, etc, but it just causes
continual headaches, unless one stays in the new package all the time -
in which case you might as well make it the user package!  The whole
rationale for a package system is to facilitate integration, which isn't
something you want to worry about when fiddling with algorithms.

There are of course exceptions to this rule, and some programming environments
cater to multiple packages, but the package system is basically a reader
hack.  As such, there are *always* going to be problems developing code,
much as there is with code that beats on the readtable in interesting ways...

							stan shebs