I'm planning a mojor release for Inline::Java 0.40. Here's what I want to put in/change:
- I::J's own code built at install time and installed with the module instead of recompiled with each Perl script. - Add a custom ClassLoader to be able to better support multiple I::J sections in a Perl script. - No more using Java from the PATH. This leads to problems with gcj mascarading as java. I will change the BIN option for a J2SDK option. Also the J2SDK specified at install time will be saved and used as the default J2SDK. You will be able to change by using the J2SDK option/PERL_INLINE_JAVA_J2SDK environment variable. - Using the "next available port number" instead of a specific port number. This would allow multiple users to run I::J in client-server mode without specifing a unique port number. In SHARED_JMV mode obviously you still need a known port.
Stuff I'm not sure yet:
- Putting I::J own code into a package to isolate it better. This is a bit complicated because of the way Java deals with the unnamed package, which is used for the users Java code.
Anyways, I'm just looking for the comments/warnings/objections/ suggestions from I::J users and the Inline community in general.
Thanks,
Patrick
---------------------------------- | Patrick LeBoutillier | [EMAIL PROTECTED]
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
