I'll repeat my previous advice. Don't use T_OBJPTR. Instead, have your XS code deal with very simple C data types and do all of the object creation/destruction in wrapper methods written in Perl (as part of your module).
The reason I advise this is exactly because XS code is so easy to get wrong and so hard to debug.
sub new {
my $ptr= xs_new( ... );
bless \$ptr, ...;
}
sub DESTROY {
my $self= shift(@_);
xs_free( $$self );
}
and
int
xs_new( ... )
WHATEVER* pObj= ...;
RETVAL= (int)pObj;
void
xs_free( self )
int self
CODE:
free( (void *)self );
- tye
-
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.
|