Re: packages, load paths and environment variables

On 4599 September 1993, Pascal Bourguignon wrote:
Holger Schauer <Holger.Schauer@xxxxxx> writes:
There is really no reason to separate package from source code files,
although it is good practice to do so.
There is one reason. The same why in Modula-2 and Modula-3 you
separate definition modules from implementation modules.
[...]

When you say that there is no reason to separate the package
definition from the sources, you're saying that there's no reason to
have circular dependencies. Well, sometimes there are reasons, but I
agree that it'd be better to avoid them.

Your points, of course, are well-taken. But I was arguing against an
inherent requirement that using packages necessarily involved a
separate file for the package definition. For simple cases, there is
no such requirement, although for complex ones there might be one, as
you rightly point out.

One may want to define "module" in such a way. 1) & 2) clearly impose
a 1:1 correspondance between modules and files.

I would rather stick with packages and defsystem then.

Holger

--
--- http://www.coling.uni-freiburg.de/~schauer/ ---
Fachbegriffe der Informatik - Einfach erklärt
135: Druckertreiber
pure virtual Araber (Martin Neumann)
.