On Mon, 10 Feb 2003 09:57:48 -0800, Clint Olsen wrote: Thanks for your quick answer.
>> What is Better Practice? >> >> PS: I'm really sorry, if this is a simple question. But I'm more a Perl >> programmer who only wants to use some existing c code from Perl. And >> however, I miss an example for this problem, e.g. via perldoc >> Inline::C-Cookbook > > The problem is Inline's inability to use code from outside libraries and > just use their header file(s) as an interface cue. This is one place where > SWIG really shines. People don't necessarily want to glob all their C in > one file for Inline to use. That's why we write libraries. Stupid question again. What's the big problem for Inline to handle it ? I can't imagine that it is so difficult to handle with extern c files, as every c compiler can, isn't it ? In my imagination, that can't be that difficult and unable to solve. A second question is still, what's the good practice to workaround Inline's inability. Just write the c library? Greetings, Janek PS: Of course, I so or so will find another way. At least I'll connect the original author to write or accept a library, what is on the long term the right way in any way. But still, I find my question interesting. I normally would all the routines called directly from Perl inlined and the rest outsourced to one or several c files, wouldn't you!? As I'm really interested in, I would also be ready to help with development, allthough I'm afraid that my c knowledge ain't good enough.
