comment on

I'm still confused as to why there should be an ambiguity about this section of the XS file:

void
MySettings::set(const string &key, const string &value)
[download]

When the error produced by the code shows that we have what looks like a matching method:

MyModule.c:64: no matching function for call to `Mysettings::set (cons
+t string *, const string *)'
/usr/local/include/mysettings.h:66: candidates are: void Mysettings::s
+et(const string &, const string &)
[download]

Does XS not distinguish well between pointers and references?

MySet does have a typemap entry, of type O_OBJECT. I'll admit my understanding of typemaps is basic; this is just taken from the combining C++ and Perl link above.

In reply to Re: Re: Writing XS frontends to C++ libraries. by kilinrax
in thread Writing XS frontends to C++ libraries. by kilinrax

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.


Your skill will accomplish what the force of many cannot
	PerlMonks