#7013: [with code, needs review] 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):

 Hi Kevin,

 I won't be able to respond on a daily basis because I'm quite busy right
 now. But concerning the above code snippet, one might use the ANSI C99
 type "uintptr_t" instead, since you obviously want to cast pointer values
 to integer values back and forth. (I can't judge right now, whether you
 really must do this, but that's another topic.)

 Using "uintptr_t" would also very benefical in light of portability to
 native Windows 64bit. Sage will not be able to support this platform
 (well, any Windows platform) for a while, but it is a goal definitely on
 the road map.

 Since on 64 bit platforms (e.g. on OS X 10.6, Ubuntu, Fedora, Suse, ...)
 we need to build Sage with "-m64", and it is not a good idea to mix "-m32"
 and "-m64", we should try hard to smooth this out of the code itself.

 Cheers, Georg

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7013#comment:6>
Sage <http://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