Hi , here are some thoughts about what we should/could do for the next release.
1) Upgrade yasm to the latest (easy) 2) Upgrade gnu config to the latest ( dont know how difficult that is , but it could fix some niggles we have , and it might simplify our specialisations. 3) Upgrade to the latest autotools/libtool ( some distros are moving over to the latest 2.2 , we may need/want to do the same , again dont know what this involves) 4) A few assembler functions to add 5) Move demo's out of the library onto the web page 6) Get rid of ancient cpus/compilers ( we will still work under C , if anyone cares) , this would simplify configure a bit , cray,pyramid, z8000,list,clipper,.... 7) Make configure run faster , I'm sure we can remove some of the tests , I can't believe they are still needed , and/or share the test results with yasm. 8) make make check parallel , it can be done. 9) Some of the changes we have made , have not been finished , finish them. 10) Split configure into two , ie standard and MPIR specific , should make the maintenance easier , this is fairly ambitious :) 11) drop support for building/running on FAT file systems ( ie file name 8.3 format) 12) simple command line build for windows ( not dependant of vcproj files) 13) fix some known bugs 14) When we update stuff , there are many places where you have to fill in the same info , make it automatic (autotools can do this , it's just not been set up that way) Some of these are trickier than others , but my aim is to simplify the system (the non-computational parts of it) Bets now being taken on what % will get done :) Thoughts? Jason -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
