Re^3: XS cannot properly handle typemap with namespace (use XSpp)

Replies are listed 'Best First'.
Re^4: XS cannot properly handle typemap with namespace (use XSpp) by llancet (Friar) on Jan 06, 2014 at 13:56 UTC
It's indeed painful for me. T_T There are two examples in the XSpp's package, and none of them fully used the XSpp's features. I spent a whole day to realize that xspp typemap should be generated to xs typemap via tools such as Module::Build::WithXSpp, otherwise you cannot use mapped types (like the "Object-WithIntAndString" example in XSpp package which used ExtUtils::MakeMaker). I also downloaded several perl packages which use XSpp, and non of them use the feature neither. Now I nearly make my code correctly compile, but I still don't understand how some errors were fixed and disappeared. And I still don't fully know the difference between "{parsed}{%precall_code %output_code}" and "{simple}{%xs_input_code %xs_output_code}". It seems the first solution don't work properly in my code. Moreover, the xspp lacks error reports. Some errors are not reported by xspp, and will just continue running silently and create malfunction xs code. You have to take hours to find clues about your bug from the final C file, and deduce the corresponding part of the xsp file.	[reply]

Replies are listed 'Best First'.

Re^4: XS cannot properly handle typemap with namespace (use XSpp)
by llancet (Friar) on Jan 06, 2014 at 13:56 UTC

It's indeed painful for me. T_T

There are two examples in the XSpp's package, and none of them fully used the XSpp's features. I spent a whole day to realize that xspp typemap should be generated to xs typemap via tools such as Module::Build::WithXSpp, otherwise you cannot use mapped types (like the "Object-WithIntAndString" example in XSpp package which used ExtUtils::MakeMaker). I also downloaded several perl packages which use XSpp, and non of them use the feature neither.

Now I nearly make my code correctly compile, but I still don't understand how some errors were fixed and disappeared. And I still don't fully know the difference between "{parsed}{%precall_code %output_code}" and "{simple}{%xs_input_code %xs_output_code}". It seems the first solution don't work properly in my code.

Moreover, the xspp lacks error reports. Some errors are not reported by xspp, and will just continue running silently and create malfunction xs code. You have to take hours to find clues about your bug from the final C file, and deduce the corresponding part of the xsp file.

[reply]