This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: 'requre' under J2EE environment
- From: Per Bothner <per at bothner dot com>
- To: Wen-Chun Ni <wcn at tbcommerce dot com>
- Cc: Kawa List <kawa at sources dot redhat dot com>
- Date: Mon, 17 May 2004 21:50:29 -0700
- Subject: Re: 'requre' under J2EE environment
- References: <20040518034117.GA20338@tbcommerce.com>
Wen-Chun Ni wrote:
I've written some Java code implementing gnu.mapping.ProcedureN
that are "required" into scheme code, which are compiled into
Java class files.
That sounds wrong. You "require" a module, not a Procedure.
When you require a class, Kawa imports bindings based on
the public fields of the class. Implementing Procedure
is neither here nor there: While Kawa compiles a module
into a ModuleBody, which is does inherit from Procedure,
you should not think of a module as a procedure.
A module is a set of bindings, plus optionally a "body"
that gets executed when it is required (if the required
lass is Runnable).
Current Java thread:
at gnu.mapping.Symbol.getFunctionValue(Symbol.java:339)
at gnu.expr.Interpreter.getSymbolProcedure(Interpreter.java:657)
I seem to remember seeing something like this recently, with a
null constraint, but I'm not sure. In principle, the constraint
should never be null.
--
--Per Bothner
per@bothner.com http://per.bothner.com/