#7013: [with code, needs work] prime_pi and nth_prime
--------------------------------------+-------------------------------------
 Reporter:  kevin.stueve              |       Owner:  kevin.stueve            
     Type:  enhancement               |      Status:  new                     
 Priority:  major                     |   Milestone:  sage-4.1.2              
Component:  number theory             |    Keywords:  primes, sieve, table,LMO
 Reviewer:  was,robertwb,GeorgSWeber  |      Author:  Kevin Stueve            
   Merged:                            |  
--------------------------------------+-------------------------------------

Comment(by GeorgSWeber):

 Silva's code states explicitly (line 25):
 {{{
 //
 // Assumptions: pointers have 4 bytes, gcc compiler
 //
 }}}
 (the first of which is plainly wrong on 64-bit systems), and has a one-
 line "compile" shell script as build system. The LMO code seems to have
 been blessed with some early version of autotools, oh well. The "optimized
 Legendre code from Andrew Ohana" seems to be missing. All these C code
 "command line programs" should go into a separate spkg. (At least this is
 what I learned from Michael Abshoff.)

 I assume that the "800 lines of code" William refers to in the fifth (or
 so) post to the sage-devel thread "are" the file "clean_prime_pi.py". I
 agree that one should look over it line-by-line (e.g. line 145 is *not*
 safe w.r.t. endian-ness), but I there's a bit more work to do ...

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7013#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" 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/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to