Hi, On Thu, Jun 24, 2010 at 6:01 AM, selva ganapathy <ganapathy_se...@yahoo.com> wrote: > Thanks Rob,Nick and Patrick , > From your analysis, I guess that JAVA + PERL with inline java and related > modules are at initial level and not to take up for application testing.
Actually, that's not really the case. Inline::Java (and most other Inline modules) have been around for almost 10 years and I think most of them are quite stable. It's just that they have been designed to call into other languages from Perl, not the other way around. However it is true that the PerlInterpreter bit in Inline::Java is in fact newer and has received less testing/usage in the field. I have also not maintained Inline::Java that much lately and realize that some issue have appeared with more recent versions of Perl. I will try to release a dev shortly that will be a bit more slimmed down: - Remove the tests that hang in the test suite ; - Remove PerlNatives from the default build choices since it's broken and not portable ; - Other small bug fixes accumulated lately. Thanks, Patrick > what I have expected is something like JEPP how PYTHON interacts with > JAVA. > Hence I have to give up my trails with inline::JAVA > > Thx for your efforts > > Selva D > > --- On Sat, 19/6/10, Patrick LeBoutillier <patrick.leboutill...@gmail.com> > wrote: > >> From: Patrick LeBoutillier <patrick.leboutill...@gmail.com> >> Subject: Re: Issue with installing Inline::Java >> To: "Sisyphus" <sisyph...@optusnet.com.au> >> Cc: "Nicholas Clark" <n...@ccl4.org>, "selva ganapathy" >> <ganapathy_se...@yahoo.com>, inline@perl.org >> Date: Saturday, 19 June, 2010, 7:11 PM >> Hi all, >> >> The PerlNatives extention is sort of a hack, as it is a .xs >> file that >> doesn't really involve Perl. I only put it in a .xs file >> to >> ease/generalize the building process. That's why those >> headers were >> not included at the time. >> >> However it seems that in more recent versions of Perl some >> macros in >> the .xs files changed in order to include (calls to|types >> from) the >> Perl API, so I guess the headers are now required. Anyways >> it's no >> harm to add them. I'll do it for in the next release... >> >> Also, the PerlNatives stuff is really experimental, as >> mentioned in >> the installation procedure. You don't really need it to >> use >> PerlInterpreter or Inline::Java. >> >> Rob and all: My apologies for not being present on the list >> lately, I >> just realized this week that I wasn't getting the messages >> anymore >> since about January. Don't know what happened, I had to >> re-register my >> email address with the list. >> >> >> Patrick >> >> On Sat, Jun 19, 2010 at 5:20 AM, Sisyphus <sisyph...@optusnet.com.au> >> wrote: >> > >> > ----- Original Message ----- From: "Nicholas Clark" >> <n...@ccl4.org> >> > >> >> The errors are consistent with not including (at >> least) perl.h >> >> Or the *right* perl.h >> >> >> > >> > Yikes ... an xs file that doesn't '#include "perl.h"' >> !! >> > Hard to envisage that would work anywhere. >> > >> > Adding the following at the very top of PerlNatives.xs >> fixes this problem: >> > >> > #include "EXTERN.h" >> > #include "perl.h" >> > #include "XSUB.h" >> > >> > and Inline-Java-0.52 (along with PerlNatives) then >> builds fine for me. How >> > about for you selva ? >> > >> > Annoyingly, the PerlNatives test script bails out >> before running any of the >> > 5 scheduled tests. The error message I'm getting is: >> > >> > t/02_perl_natives.t .. Unexpected exception of type >> > 'java.lang.UnsatisfiedLinkError': RegisterMethod at >> > >> C:\_32\comp\Inline-Java-0.52\blib\lib/Inline/Java/Object.pm >> line 49 >> > >> > Something to look at tomorrow .... thanks Nicholas. >> > >> > Cheers, >> > Rob >> > >> > >> >> >> >> -- >> ===================== >> Patrick LeBoutillier >> Rosemère, Québec, Canada >> > > > > -- ===================== Patrick LeBoutillier Rosemère, Québec, Canada
