Subject: | not thread-safe (and other nits) |
Hi Martin,
I'm filing this bug report since the module uses the same technique and
even more or less the same code as Class::XSAccessor did a long time
ago. Since then, C::XSA has evolved a lot and chocolateboy and I have
spent quite some effort to optimize it, make it thread-safe, and
generally more safe to use.
I wonder whether it would be possible and make sense to use C::XSA
internally instead of having an (old) fork of the code. C::XSA has
become complex enough to make a synchronization difficult to impossible.
If the mechanisms that C::XSA provides for installing accessors is too
limited or cumbersome for your module to use, let me know and we'll
figure out how to improve it.
Cheers,
Steffen