On 2011-07-25 15:40, John Cremona wrote: > A second point Karim made is that he would like to see more more cases > (currently: 0) in which a deficiency in a part of Pari used by Sage > -- for example, some number field functionality -- was fixed by > contributions to Pari itself, rather than by adding the extra > functionality within the Sage library.
There are certainly a lot of PARI bugs which were discovered through Sage and then patched in PARI. Regarding PARI contributions: I simply think that Sage is much more developer-friendly than PARI. One, because programming in Sage is much easier than in PARI and second, because there is a "Sage community" but no "PARI community". You cannot really blaim PARI for using C as a programming language (it is also because of historical reasons), but I think there can be some blaim for being such a closed community of essentially 2 developers. There isn't even a working PARI mailing list... which I think is really a pity. Cheers, Jeroen. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
