In that report, William Stein says, "A large amount of the symbolic functionality that uses Maxima has issues like this, but unfortunately there is basically nothing we can do about it, except continue with projects to rewrite the parts of Sage that call Maxima so that they don't call Maxima."
Which is clearly untrue. Here is one obvious alternative: You or someone else, can look at the (open source) Maxima code and try to fix it. As for Bondarenko submitting 100 bugs to WRI and WRI accepting 90 of them ... I would expect that they were 90 instances of one or a few bugs. As for working around it, Bondarenko is not interested in work- arounds. He is not interested in the result of this computation, which was probably artificially generated by randomly clumping together stuff. He is interested in finding bugs. RJf On Jul 4, 10:44 pm, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > This bug > > http://sagetrac.org/sage_trac/ticket/6423 > > was reported by someone outside the sage project, but who potentially > could contribute - he writes software for testing computer algebra > systems, and seems to succeed in finding quite a few bugs. I believe he > submitted 100 once to WRI, of which I believe about 90 they accepted > were bugs. > > He is certainly trying to get commerical backing, but one never knows, > he might just be useful. > > It would be nice to give him some feedback on how to work around it, > rather than just say its a Maxima bug. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
