improved module support in kawa

[Per Bothner <per at bothner dot com>]

I just checked into cvs some changes related to modules
that I think give Kawa are more full-fledged module system.
You now also have better control over the generated class,
so you can often write a Scheme module where you need a
Java class with specific properties.  See the manual
for more information.

I also did some cleanups, and make some other changes:

The new declaration (module-export name ...) allows control over the
names exported from a module.  The new declaration (module-static ...)
allows control over which definitions are static and which are
non-static.  This makes it easier to use a module as a Java class.

Procedures names that accidentally clash with inherited method
names (such as "run") are now re-named.

Simple aliases (define-aliases defining an alias for a variable name)
are implemented more efficiently.

The package hierarchy is getter cleaner, with fewer cyclic dependencies:
The gnu.math package no longer has any dependencies on kawa.* or gnu.*.
Two classes were moved from gnu.text to other classes, avoiding another
cyclic package dependency between gnu.text and gnu.mapping.  The new
gnu.kawa.lispexpr is for compile-time handling of Lisp-like languages.
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/