"Julian Seward (Intl Vendor)" wrote:
>
> Sounds like some kind of rts/code generation bug. We fixed a
> few in 4.08, so the recently released 4.08.1 might work better.
> As usual the best thing you can do is send us a test case
> showing the problem; can you do that?
Sadly not because this was at the top of a huge mountain of code which
I have changed too much since reporting the bug. I managed to remove the
bug anyway in the end by removing a duplicate multi-parameter class
definition. File 1 defined class A x, class B y, and class (A x,B y) => C x y.
It also declared instance (A x,B y) => C x y. File 2 declared (wrongly I suppose)
a duplicate instance (A x,B y) => C x y, plus a specific instance C P Q.
File 3 used a function on C x Q, assuming C x Q as context. Removing the first
instance of (A x,B y) => C x y solved the problem. If you want code that actually
reproduces the bug I MAY be able to get back to the situation of several days
ago, but don't count on it.
