But as you said, example 4 is aim to access to functions in source, in this scenario, Inline C is not very suitable I think, although what h2xs shows in example 4 in perlxstut is not good either.

Hi,

Sure its perfectly suitable see

https://metacpan.org/pod/distribution/Inline-C/lib/Inline/C/Cookbook.pod#Exposing-Shared-Libraries

Might see also https://metacpan.org/pod/FFI::Platypus#libuuid

Interfacing Perl with C++, using XS, with external files, and using the STL as parameters and return values.

https://www.manning.com/books/extending-and-embedding-perl

...

In reply to Re^3: some questions about example 4 of perlxstut by Anonymous Monk
in thread some questions about example 4 of perlxstut by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.