Alec, It all depends on what exactly you want to do, but here are a few things to consider:
- I found it's best to keep the interaction between languages to a minimum. Maybe the best solution is not to wrap the entire API but to write Java code that provides functions specific to your project that help keep the boundary clean. - Inline::Java should be able to provide the public interface for any object, even iterators and containers. But if you have a big iterator/container, remember that every time you access an object in the iterator/container you need to go get the object reference in Java and create a stub for it in Perl. That takes time. - If you wrap a large API with lots of calls, consider using JNI. It's a lot faster when you make many calls. If possible, give more information on the nature of the API and what you need to use it for. That way maybe we can give you more specific information. Cheers, Patrick ----- Original Message ----- > G’Day, > > I am trying to wrap a large Java API for use in Perl. Currently I am > having > trouble trying to understand how to even begin. > > Should I write Java to make the API look more Perl-ish and what would > that > Java look like? > > OR > > Should I just expose the API as is in Perl, then how to I handle things > like > iterators and containers (there are lots of object containers)? > > The only guidance I can find is this > http://www.perl.com/lpt/a/2003/11/07/java.html > > Anyone got any suggestions? > > Thanks > > > Alec Clews, <[EMAIL PROTECTED]>, Melbourne, Australia > http://www.geocities.com/alecclews/ > > > > Find local movie times and trailers on Yahoo! Movies. > http://au.movies.yahoo.com > >
