Re: Module Considerations

[Per Bothner <bothner@cygnus.com>]

Some more for your list, some more important than others.

@item
Should be able to wrap one or more existing source files containing
various definitions as module without modifying any of the souce files.
(Can be handled with some kind of "include" mechanism.)

@item
The module control language should be Scheme.  A module definition
should be mixable with other module definitions and regular
Scheme definitions in a single source file.

@item
Must be able to create a module from existing modules.

@item
A module (a source-code construct) maps into (evaluates to, or at least
names) a package/environment, which is a first-class Scheme object.

@item
Avoid ugly non-Scheme syntax (e.g. prefix comma) for manipulating modules,
even in top-level read-eval-print loop.

	--Per Bothner
Cygnus Solutions     bothner@cygnus.com     http://www.cygnus.com/~bothner