[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [SVN RFC] Making JavaHL easier to maintain?

From: David James <staple_at_gmail.com>
Date: 2004-09-03 19:39:59 CEST

Here's what Patrick wrote on Tuesday:
> I would not considering it upgrading for javahl to use SWIG. From my
> point of view generating the JNI header is no problem at all. I use an
> ant script in my java ide for it. If I had to regenerate the SWIG code,
> I always had to start a new working copy. That is much more of a problem.

But doesn't SWIG offer benefits beyond generating the JNI headers?

A quote from the SWIG documentation: http://www.swig.org/Doc1.3/Java.html
"[Using SWIG] is different to using the 'javah' tool as SWIG will wrap
existing C/C++ code, whereas javah takes 'native' Java function
declarations and creates C/C++ function prototypes. SWIG wraps C/C++
code using Java proxy classes and is very useful if you want to have
access to large amounts of C/C++ code from Java. "

The question is, how much will those capabilities benefit us?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 3 19:40:15 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.