Thanks! I did some initial testing with this (which did work with some trickery upstream), but I believe what I'm going to do is remove all access to the C functions by their original names, and hide all of that so I don't have to do trickery or other things.
If people want to use Perl, I'm thinking they are used to certain idioms, so perl style function calls are best. I don't remember why I offered the original C names anyway, probably because it was my first foray into wrapping C.
I've learned a lot about wrapping libraries and some XS, and am burned by some initial decisions. Thankfully, most of the underlying core of my projects are not used directly, so I can muck with the API without much damage other than (hopefully) people I know are testing/working it.
In reply to Re^2: Accessing an XS function from a Perl function of the same name
by stevieb
in thread Accessing an XS function from a Perl function of the same name
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |