Patrick LeBoutillier wrote:
>
> I've just uploaded Inline::Java 0.21 to CPAN.
>
> It is a minor upgrade that includes class 'studying', small bug fixes and some
>performance improvements.
>
> The next release should be Inline 0.40 compatible.
>
> Patrick
Patrick,
I had an idea for Inline::Java. Let's say that you had an Inline wrapper
class inside a Perl module. You should be able to make a distribution
(easy with the new Inline 0.40 features) and distribute the module to
various people. Then you could run a server script on one machine and
have the others use your Inline::Java based module remotely:
NewModule.pm
---8<---
use Inline Java => 'DATA',
NAME => 'NewModule',
VERSION => '1.23',
IMPORT => ['listen', 'connect'];
# Perl code goes here.
__DATA__
__END__
class NewThing {
public NewThing() {}
public DoIt() {}
}
---8<---
ServerScript.pl
---8<---
use NewModule;
NewModule->listen(3456);
---8<---
ClientScript.pl
---8<---
use NewModule;
my $c1 = NewModule->connect('my.server.com', 3456);
my $j1 = $c1->NewThing->new();
$j1->DoIt;
---8<---
I'm sure there's a lot of details I missed. But does it seem like a good
idea? Perhaps you can start a discussion with Mark Ethan Trostler
(Java.pm) and come up with some collaborative ideas. I think there's
room for both Java and Inline::Java. Java.pm seems to make use
precompiled Java, where Inline compiles it on the fly for small hacks or
better Java/Perl glue/interface control. Java.pm already does the remote
thing. I think there's crossover and room to share code.
The JPL thing seems to have lost traction. Since the 2 of you have
energy to move forward, why not team up and include the people on the
JPL mailing list who still have a strong interest.
My two cents, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
