Re: Perl bindings for Subversion using SWIG

On Mon, 27 Jan 2003, Greg Stein wrote:

  If you aren't an expert with either SWIG or XS my guess is that Inline::C
  is probably the easiest way to do this. Of course, I idly tried working
  on a Subversion wrapper using Inline::C, and I got nowhere. But I really
  don't know much about C, and I didn't try all _that_ hard.

 I'm not familiar with Inline::C, but get the impression it is about
 inserting C code into Perl code? Does that mean you would have to manually
 write a Perl function for each SVN function you want to expose? And then
 update those mapping functions every time we change the SVN API?

 How, um... tedious... :-)

Yeah, that would be, but it's not like that. Actually, Inline
automatically makes C functions available at the Perl level.

Of course, you might want to write some Perl level code to make the API
more Perl-ish. In fact, one of the great sins of some Perl-wrapping-C
code, IMHO, is to _simply_ wrap the C interface and present it as is.
That makes for a really bad Perl interface.

But this is getting OT.

-dave

/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:19:41 2006