shebs@utah-orion.UUCP (03/30/87)
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