Hi,
[ snip ]
Show quoted text> Fixing this would be nice, but that
> might break other modules that relies on the current behaviour, so I
> have been reluctant to fixing this.
Can you clarify what you mean by "relies on the current behaviour"? I mean, the current behaviour is that subclasses don't work reliably, or at least that's how I read your response (in combination with our analysis of the problem so far). Obviously, nobody can truely depend on the current behaviour as their subclasses won't work. What is the change in behaviour that you implemented that other modules may depend on?
Show quoted text> I haven't decided whether the best thing is to fix Math::BigInt etc.
> or to create a new set of distributions, for instance
> Math::BigInt::OO, Math::BigFloat::OO etc.
>
> Suggestions or recommendations are welcome!
In order to determine what "other modules" there are that might rely on the current behaviour, I've queried the reverse-dependency-graph for Math::BigFloat on MetaCPAN (
https://metacpan.org/requires/module/Math::BigFloat?p=1&size=100&sort=%5B%5B2%2C1%5D%5D).
It seems there are 48 public modules which depend on Math::BigFloat. This seems like a mnageable set of modules we can test against the change you have developed to see what happens when you change Math::BigFloat. I'd be willing to help run the test frameworks of these modules and see what happens before and after the change you have for now, if you think that'd be an acceptable estimate of the problems that are likely to ensue from your changes.
(BTW, maybe I can help with more feedback if I can see the changes you're thinking of applying. Is there anywhere I can see the new version of the code?)
Regards,
Erik.