Kawa applications/projects?

[Paul R. Potts]

The manual could still use a section entitled "using Kawa as an embedded
scripting language" right in line after the "compiling scheme code to
byte-codes" section and before the "Extensions" section.

Really, I see this is an important use for kawa: being able to, from another
Java program (applet, application, etc.), create a new environment and
interpreter combination, execute commands, set values, retrieve values, and
eventually exit. It is the whole rationale behind our use of Kawa.

I will volunteer to write this section, but I am still having a great deal
of trouble making sense of environments, environment chaining, and their
relationship to bindings and the interpreter object. It seems like these are
viewed as secondary means of accessing the Kawa tool but from our
perspective, it is the front door. I try to read the source and watch it
execute to understand this better, but things get a little out of control
when the interpreter builds a stack thirty levels deep working on a
relatively simple expression.

Paul