jakarta-bsf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sonny To" <son.c...@gmail.com>
Subject Re: A question ad your suggested Jython-engine patch (Re: Fwd: BSFManager.setClassLoader doesn't seem to work
Date Sun, 29 Oct 2006 07:05:54 GMT
On 10/28/06, Rony G. Flatscher <Rony.Flatscher@wu-wien.ac.at> wrote:
<http://wi.wu-wien.ac.at/rgf/rexx/bsf4rexx/docs/docs.apache.bsf/org/apache/bsf/BSFEngine.html>)
>       and what they are meant for:
>          1. "exec(...)": Java coder needs to execute a script, there are
>             no arguments to be passed to the script nor is there any
>             return value expected,
>          2. "eval(...)": Java coder wants to evaluate a script, does not
>             need to supply any arguments, but expects a return value,
>          3. "apply(...)": Java coder needs to execute a script, needs to
>             supply arguments to the script and *is* expecting a return
>             value,
>          4. "call(...)": Java coder wants to invoke a method in a
>             script, supplying arguments and expecting a return value.
>
> So you see, your patch would only alleviate the class reference issue in
> the Jython engine for case # 1, where it probably could also help in
> cases #2 and #3. (Maybe also for a  "compileScript(...)" method if that
> makes sense in the context of Jython.)

case #4 doesn't seem relevant for my patch... here's a patch for case
#1 to #3 to import packages

Mime
View raw message