Hello Monks,

I am trying to test the functionality of Inline::c with small examples. For one shown below, I seem to get the result alright when I execute test.pl, still I want to take suggestions from you all. Please guide if I am doing it properly.

One more thing, suppose if I have a .dlls/c-libraries instead of the c-source code, will the approach remain the same? Any alternative ways? Basically, I want to keep perl code and .dlls/c-libraries in separate folders.

Hail Monks!

Raj 

test.pl
--------------------
use hello qw(addint);

my $a=addint(9, 16);
print "$a\n";
exit;


hello.pm
------------
package hello;
use strict;
require Exporter;
@ISA=qw(Exporter);
@EXPORT_OK=qw(addint);

use Inline (C => 'cfunction/addint.c');
1;


addint.c
-----------------------------
int addint(int x, int y) {
  return x + y;
}

[download]

In reply to Re: Inline::C query by newbio
in thread Inline::C query by newbio

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.