On Tue, Jan 13, 2009 at 6:29 AM, Martin Albrecht <m...@informatik.uni-bremen.de> wrote: > >> In particular the class >> >> cdef class Polynomial_zmod_flint(Polynomial_template): >> >> only has like 5 or 6 methods. Just make a version of this class that is >> >> cdef class Polynomial_zmod_flint_and_ntl(Polynomial_template): >> >> say that defines versions of all 5 or 6 methods that use both ntl (or >> any solid known code) and flint in parallel, and checks that each >> function does the same thing. Then run it, and when it bombs you'll >> see exactly what type your made in the flint wrapping or bug there is >> in flint (or ntl). > > Hi, > > the class has many more methods which are kinda automatically handled (see > libs.flint.zmod_poly_linkage.pxi). I tried your approach to some extend:
I see. I underestimated how clever you were being with your code :-) > See all the statements like this in polynomial_template.pxi > > #assert r._parent(pari(self) - pari(right)) == r > > I didn't cover every method but so far nothing was picked up. I'll try to > extend the coverage of these assert statements. Yes, I hope finishing this should reveal the problem. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
