Am Mittwoch, 9. Juli 2014 17:27:21 UTC+2 schrieb Volker Braun: > > IMHO its better to go with the first option. You essentially want to add a > single new method to matrices, it'll be easier to write and maintain to not > have to dig through a layer of Python->C++ indirection. > > The linbox code of course uses the LinBox C++ matrix class. Then there is > always some song and dance about getting the matrix data to linbox and back > into Sage. If you think its confusing then that is precisely why you should > go with A) to avoid it. Hint: At the end of the day, all dense matrices are > in C storage order in memory. > > Thank you for your posting.
I learned quite a few things from the responses of the people here, and when the problem is (hopefully) solved I will compile what I have learned. Version A sounds great if having it as a sage module is the ultimate goal, but having it as a sage module is just part of it and I'd have to talk it out with my supervisor before I change ways this radical (even though I'm sure I'd be able to convince him if statistics would show it to be fast enough for his purposes). Also, after this single function is added, more functionality should follow. Another target is Alekhnovichs algorithm. Maybe in the end I'll regret not using cython from the beginning. I found out a portion of my problem might have originated from outside sage and have complicated matters for me and I might have been near the solution I wanted, even though I didn't know it. Regards, David -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
