On 3 Nov, 15:41, William Stein <wst...@gmail.com> wrote: > On Wed, Nov 3, 2010 at 7:47 AM, Bill Hart <goodwillh...@googlemail.com> wrote: > > > On 3 Nov, 12:55, John Cremona <john.crem...@gmail.com> wrote: > >> > Sage on Solaris? And if Pari doesn't even have a comprehensive test > >> > suite and a new stable release I'm not getting why we are even using > >> > it the way we are. We surely need to be much more sceptical about it > >> > and test the hell out of it before trying to put it into Sage. OK it's > >> > in now, but is it really worth doing it that way again in the future? > > >> Pari has a test suite of about 3200 lines. > > > There's about 50,000 lines of test code in flint and it does a > > fraction of what Pari does in terms of functionality. > > Michael Abshoff posted the SLOC count for Pari a while ago > (here:http://www.mail-archive.com/sage-devel@googlegroups.com/msg06440.html). > The line for pari was: > > 120578 pari-2.3.2.p3
So 117378 lines of code vs 3200 lines of test code for Pari. Around 20000 lines of code vs 20000 lines of test code for flint2. > > He remarks "There are some real surprises on that list. MPFR has many > more lines of code than I thought, Pari many fewer lines of code. It's > amazing what it achieves with such a small code base." > > So, despite FLINT doing only a fraction of what Pari does in terms of > functionality, Pari isn't that much bigger than FLINT. In fact, > Michael even goes on to remark that "FLINT is a bloated pig...". :-) > Yeah but it runs really fast, and he was right. Why do you think we rewrote it from scratch. > > > > > > > > > >> This may not be as > >> comprehensive as you would like, but it includes calls to every gp > >> function, and extra tests are added every time a bug is reported and > >> fixed. Moreover, this test suite is run on installation in Sage (if > >> SAGE_CHECK or something similar is set, e.g. during the testing > >> process before the new spkg is accepted). > > >> Secondly, partly as a result of all the testing of Pari by Sage > >> developers (and bugs found and fixed, some by Sage developers and > >> others by on of the two Pari developers), Pari has announced a new > >> stable release, essentially the one which is now in Sage, once it has > >> been through a lot more tests (there's a build log > >> athttp://pari.math.u-bordeaux.fr/buildlog.htmlwhichto my amateur eye > >> looks similar tohttp://build.sagemath.org/sage/one_line_per_build > > > That is good news! I was very disconcerted when we were told we should > > be putting Pari SVN in Sage. I understand the issues with developer > > manpower there, but this is precisely why I think we've not been doing > > the right thing by expecting it all Just Works. > > We switched to Pari SVN for several reasons including being told by > Karim that the time was right and that a stable release based on it > was "coming soon". Great! Git version of flint 1.6 is available here: http://selmer.warwick.ac.uk/FLINT.git branch test_code. The time is right and a stable release based on it is "coming soon". In fact I will do you one better. No known issues! Please report any bugs and we'll fix in git. > > > > > > > > > > >> Bill, wouldn't you be an ideal person to help get MPIR 2.1.3 into > >> Sage? I would certainly like everything to run twice as fast! > > > If I understand correctly, there aren't issues with the MPIR spkg. The > > issues are with Sage rebuilding library dependencies when they are > > updated. That's not something I have any expertise worth a dime to > > help with. > > > Bill. > > > -- > > 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 > > athttp://groups.google.com/group/sage-devel > > URL:http://www.sagemath.org > > -- > William Stein > Professor of Mathematics > University of Washingtonhttp://wstein.org -- 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
