I don't know the semantics of PL_markstack_ptr, but I would guess that it's an internal detail that might be subject to change in the future. If it does, I'd be happy to let the Inline::C maintainers deal with that and not have to re-release all my Inline-derived modules. While the XS you point at might look awkward, that only comes out to about 4 processor instructions more than your improved version, so I doubt there is any performance difference.
If you think there is a reliable way to avoid that dance, maybe contribute a patch to Inline::C instead? I mean, Inline can look at the C source code and try parsing it to find out if it is actually pushing things onto the stack.... maybe.
In reply to Re: [XS] Manipulating the Stack
by NERDVANA
in thread [XS] Manipulating the Stack
by syphilis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |