#4000: Implement QQ['x'] via Flint ZZ['x'] + denominator
------------------------------+---------------------------------------------
 Reporter:  malb              |         Owner:  somebody                        
                          
     Type:  enhancement       |        Status:  needs_work                      
                          
 Priority:  blocker           |     Milestone:  sage-4.6                        
                          
Component:  basic arithmetic  |    Resolution:                                  
                          
 Keywords:                    |        Author:  Sebastian Pancratz, Martin 
Albrecht                       
 Upstream:  N/A               |      Reviewer:  John Cremona, Martin Albrecht, 
Alex Ghitza, Harald Schilly
   Merged:  sage-4.6.alpha1   |   Work_issues:  Solaris build error, doctest 
error                        
------------------------------+---------------------------------------------

Comment(by leif):

 Replying to [comment:101 drkirkby]:
 > It would be a lot less confusing if people used gcc to compile C and g++
 to compile C++. What next, g++ to compile Fortran?

 Note that {{{gcc}}} is not the C compiler, but a compiler ''driver'' (and
 GCC is the GNU ''Compiler Collection'', renamed years ago).

 So it's in general pretty ok to use {{{gcc}}} to preprocess, assemble or
 link files, compile C, C++ or even Fortran files with {{{gcc}}}, but one
 should pass the appropriate options (and e.g. libraries that are ''not''
 added by default in that case) depending on the source language.

 Of course using {{{gjc}}} for Java, {{{g++}}} for C++ and {{{gfortran}}}
 for Fortran is less confusing (and perhaps less error-prone).

 > It would be nice to get rid of the endless warnings like:
 >
 {{{
 cc1plus: warning: command line option "-Wstrict-prototypes" is valid for
 Ada/C/ObjC but not for C++
 }}}

 Again ''ceterum censeo ...'' (I don't recall how often I complained about
 that).

 Also, (besides {{{libcsage.*}}}) {{{libstdc++.*}}} is linked to each and
 every extension module regardless of the {{{language}}}.

 Note also that the XPG6 / C99 issue is not an upstream (FLINT) problem,
 since FLINT is C, not C++, but we compile FLINT source code as C++.

 In addition, the Solaris headers are patched by GCC's {{{fix-includes}}},
 so I'm not sure who's to blame for the failure. The relevant test should
 certainly also make a distinction on C++.

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