I've been tinkering a bit, and found the following baviour: When the Classfunctions of the c++ class are placed in the headerfile or the class is directly defined in the head of the .xs file like this:

 class foo {
public:
  foo(int a) {
    value = a;
  }
private:
  int value;
}
[download]

(like in http://www.johnkeiser.com/perl-xs-c%2B%2B.html another neat XS/C++ source), everything works as expected. The moment the class-definition is separated from the actual code, eg. having a .h and a .cpp file, the tests begin to fail. Additionally, reproducing EXMAPLE 4 of perlxstut (including a pure c lib with separate .h and .c files, no c++) works just fine.

Conclusion:

From what I see, the problem is somewhere located in the process where libmyclass.a is bound into Mytest.so, or in the creation of libmyclass.a itself.

PS: This is my first time posting something on perlmonks, and writing about your problem really hepls to think about it.wow. Any maybe this thread will help another lost XS-Soul on their journey...feels good, man :D

---

---

• 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.