Re: Inline::C error.

First off, you need a C compiler, second.. Inline::C will try to create some really weird looking filenames and directory names. I'm not sure how exactly Inline would work on Windows. You don't need any XS knowledge to use Inline but it may came in handy :)

BTW: I dropped Inline for XS a while ago so I'm actually not all that much help. Just my $ 0.02 really...

Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.

Comment on Re: Inline::C error.

Replies are listed 'Best First'.
Re: Re: Inline::C error. by gjb (Vicar) on Jan 03, 2003 at 23:35 UTC
Would you mind commenting why you dropped Inline::C? I'm currently facing a similar dilemma and I feel more like going with XS since Inline::C adds and additional level to the debugging process (reporting errors in the XS file it automatically generates). Thanks in advance, -gjb-	[reply]
Re: Re: Re: Inline::C error. by Beatnik (Parson) on Jan 03, 2003 at 23:57 UTC
Well, Inline is nice (Ingy++ for that one), but it requires the extra overhead when compiling/linking. It seemed a bit silly to me of using Inline::C to eventually generate stuff XS does itself. IIRC I benchmarked it somehow and it appeared that pure XS was still faster than Inline (which kinda makes sense). Inline::C was a bit confusing at the time but the ppl on the mailing list were extremly helpfull :) Guess I just like it the old fashioned way^tm Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply]