Another alternative is to use Inline::C. This reads 'Myfile' correctly for me:

use warnings;
use Inline C => <<'EOC';

#define DSZ 108

struct stud
{
        char name[100];
        int roll_no;
};

struct student
{
        struct stud s;
        int grade;
}value;

void foo(char * fn) {
     FILE *fps;
     int n;
     struct student *buffer=(struct student*)malloc(sizeof(struct stud
+ent));
     fps=fopen(fn,"rb");
     n=fread(buffer,DSZ,1,fps);
     printf("Name:%s Grade:%d NO:%d\n",buffer->s.name,buffer->grade,bu
+ffer->s.roll_no);
     fclose(fps);
}

EOC

foo("Myfile");
# outputs:
# Name:myname Grade:1 NO:149
[download]

It's trivial to return the values to perl, if need be (rather than simply print them to stdout). And if it's necessary to use perl's IO abstraction interface (see perldoc perlapio) instead of the usual C functions, then I think that could be accommodated, too.

Cheers,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.