I must take a close look at your actual code. If it's sufficiently general I'll probably change Pixie to make use of it rather than having its own specific implementation. | [reply] |
Feel free. I'm new to XS and it's been a long time since I've written C. It's very possible I've screwed something up. One thing off the bat that bugged me was processing multiple optional arguments in XS( ... )
All of the XS functions are "wrappers" to call the C functions. The reason I did this was for some reason (probably something stupid I was doing), I was getting strange behavior when trying to add support for the optional parameter processing. Just saying SvROK(someSV) would dump core. I coded around it not knowing why it was doing it which in general is a bad idea IMHO. Though if the "slotname" (the optional name) isn't going to be optional I can happily ditch it without worry.
-Lee
"To be civilized is to deny one's nature."
| [reply] |