You woud need to (load "@java/java+.l)" to load all the java interoperability functions.
Question to the audience: should I then add said function to the ersatz launch script as part of the changes? How do I add it to pil? Another question to the audience: I could replace my jar with the mainline jar, then advice users to mkJar so that they get a jar file containing my changes. Is it advisable? (As you may notice, I may be at least five years younger than you.) Samuel Dennis R. Borlongan On Fri, Jun 27, 2014 at 3:19 AM, Christophe Gragnic < christophegrag...@gmail.com> wrote: > On Thu, Jun 26, 2014 at 5:54 PM, Samuel Dennis Borlongan > <srborlon...@gmail.com> wrote: > > Try replacing the picolisp.jar file with the mainline jar. > > > > What I usually do is to call mkJar with the original jar, which then > builds > > my version. > > > > The problem with my version of the jar is that I've been running Java 8 > > since the beta existed 6 months ago, so every time I cal mkJarWin, the > > resulting jar only works in Java 8. > > Thanks Samuel. I managed to build the .jar using a C/ASM Picolisp > (irony!) but my problem is that I don't understand how to use your > interop lib: how to load the files in your java dir? > When I call ersatz/pil, javaImport is still NIL. > I guess I'm missing something obvious. > > > chri > > -- > > http://profgra.org/lycee/ (site pro) > http://delicious.com/profgraorg (liens, favoris) > https://twitter.com/profgraorg > -- > UNSUBSCRIBE: mailto:firstname.lastname@example.org?subject=Unsubscribe >