> From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] > Sent: Saturday, December 07, 2002 8:45 AM > To: Nick Sieger > Cc: [EMAIL PROTECTED] > Subject: RE: BanInfo wizard anyone? > > Well, I didn't, but the beanshell is still directly > involved. Elisp > > sends strings to the beanshell which invokes java code, > and java code > > invokes interfaces which, through a proxy, print lisp forms back to > > stdout and are evaluated by `bsh-eval-r'. > > > > > Nick, > > Would the Java side be able to define an interface for and invoke > (through the proxy) Lisp functions that take arguments. Your example > showed invocation only of a parameterless function. If so, > I think your JUCI is very elegant and hope that you will proceed > with its development. I'd be glad to incorporate it into the > JDEE for you or get you commit authorization for the JDEE CVS > repository so you could do it yourself.
It would most certainly handle java and/or lisp functions that take arguments, although I've done limited testing up to this point. I'm getting comfortable with how the general framework is shaping up at this point, but I imagine as it receives more practical use we'll run up against certain combinations of java/elisp objects that won't translate properly. But I don't expect those types of issues to be too difficult to solve. I'm working on documentation and cleaning up the code. I'd be happy to send you a copy of the code before you consider allowing me to have commit access. One small questions for you: How often do you upgrade beanshell versions, and what kind of considerations need to be taken into account before upgrading? I grabbed a recent version (1.2.7) of the beanshell and started developing against it rather than the version currently being distributed w/ the JDEE. I don't recall right now what caused me to upgrade, I'll have to dig that information up again. If need be I can rollback the version and figure out how to make it work with the current version. /Nick
