Inline::C can still be helpful - as a quick way of discovering what's going wrong and testing proposed fixes.

For example, I placed (copy'n'paste') your 2 functions in an Inline::C script: 
use warnings;
use strict;

use Inline C => Config =>
  BUILD_NOISY => 1;

use Inline C => <<'EOC';

void print_array_char(char * array) {
        int l;
        int i;
        l=strlen(array);
        printf("Length of array is %d\n",l);

        for(i=0;i < l;i++) {
                printf("Element array[%d] = %c\n",i,array[i]);
        }
}

void print_array_int(int array[], int l) {
        int i;
        for(i=0;i < l;i++) {
                printf("Element array[%d] = %d\n",i,array[i]);
        }
}

EOC

print_array_char( "revendar" );
print_array_int (-1,12,23,3);

[download]
When I run that script, it compiles, then outputs: 
Length of array is 8
Element array[0] = r
Element array[1] = e
Element array[2] = v
Element array[3] = e
Element array[4] = n
Element array[5] = d
Element array[6] = a
Element array[7] = r
Undefined subroutine &main::print_array_int_alt called at try.pl line 
+....

[download]
The problem is that, although there's nothing syntactically wrong with print_array_int(), perl doesn't know how to pass the 'int array[]' type to XS.
For a working solution, you need to know a little bit about the perl API. I suggest perlxs, perlxstut, and perlapi docs, though you'll perhaps also find some useful tips in the Inline::C cookbook and, no doubt, many other places.
Anyway, here's one solution: 
void print_array_int(int x, ...) {
  dXSARGS;
  int i;

  for(i=0;i < items - 1; i++) {
    printf("Element array[%d] = %d\n",i,SvIV(ST(i)));
  }
  XSRETURN(0);
}

[download]
"items" is the number of elements on the stack - so there's really no need to pass the length of the array to the function. You could remove that arg and rewrite the for loop condition as (i=0; i<items; i++)

Two things to note about Inline::C:
1) It's really just XS - it takes your C code, autogenerates the XS code, then compiles and runs your program.
2) Inline::C defines its own stack macros, all of which begin with "Inline_Stack_" and are defined in the Inline.h file that it also autogenerates. Other than that, it's the same as XS, and you don't *have* to use its stack macros. You can just use the normal XS terms - as I did above when I declared "dXSARGS" instead of "Inline_Stack_Vars" (and used "XSRETURN(0)" instead of "Inline_Stack_Void").

Cheers,
Rob

In reply to Re^3: Perl XS by syphilis
in thread Perl XS by revendar

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.