Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Re^4: XS, raspberry pi, and a hundred bucks

by perlfan (Vicar)
on Nov 02, 2021 at 01:58 UTC ( #11138318=note: print w/replies, xml ) Need Help??

in reply to Re^3: XS, raspberry pi, and a hundred bucks
in thread XS, raspberry pi, and a hundred bucks

That seems fair - mind explaining why? I am only asking for my own edification. I've written exactly one XS module on CPAN, and I had a lot of help; but I can say for sure that any use of Inline::C has not been for anything I plan to distribute broadly. That said, the one difference I can see between the 2 is that XS modules are compiled once on install; Inline::C run the risk of being recompiled if the cache goes away - usually at an inopportune time.
  • Comment on Re^4: XS, raspberry pi, and a hundred bucks

Replies are listed 'Best First'.
Re^5: XS, raspberry pi, and a hundred bucks
by Anonymous Monk on Nov 02, 2021 at 08:31 UTC
    Indeed Inline::C generates an xs distribution, you only have to use it once to bootstrap an xs module

      Hmmm, yes and no. Because I did not find a straight forward way to tell Inline::C NOT to cleanup XS code after successful compilation. From its source code, the cleanup option is in {API} hash which I do not know how to affect. The very round-about way of doing this was to break the compilation by introducing an obvious error in the C code. That would leave the XS file in the build dir. Albeit broken but easily fixable. That's all based on my own experiments as documentation is a bit scarce. It would be a good feature to allow for converting the hidden XS distribution to a stand-alone module in a straight-forward way. (Edit: see Anonymous response below with proper solution)

      On the very serious other hand, NERDVANA mentions Inline::Module (unknown to me a minute ago) which provides exactly this functionality. I have not tried it yet.

      FWIW, this tells Inline::C to place the output binaries to specific directory ("unhiding" it!) - provided output dir exists. BUT I did not manage to tell it to NOT cleanup so that I can use the XS code. So I can only use the binaries. (Edit: same as above edit)

      use Inline C => Config => # dir must already exist! DIRECTORY => 'xxx' ; use Inline 'C'; # perl code ... __END__ __C__ // C code

      bw, bliako

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11138318]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (2)
As of 2022-01-25 17:36 GMT
Find Nodes?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:

    Results (67 votes). Check out past polls.