#5396: Wrapping lcalc library
------------------------------------------+---------------------------------
   Reporter:  rishi                       |       Owner:  Rishi       
       Type:  enhancement                 |      Status:  needs_review
   Priority:  major                       |   Milestone:  sage-4.3.2  
  Component:  number theory               |    Keywords:  lcalc       
     Author:  rishi, ylchapuy             |    Upstream:  N/A         
   Reviewer:  John Cremona, David Kirkby  |      Merged:              
Work_issues:                              |  
------------------------------------------+---------------------------------

Comment(by drkirkby):

 Replying to [comment:63 mrubinst]:
 > One more thing- I've also cleaned up my makefile a bit, and, in the
 source, got rid of depreciated headers and unused variables.

 That is really '''excellent''' news. Is there any chance either you or I
 could check this with the Sun compiler on Solaris, before you make an
 official release? The Sun compilers more fussy than gcc, but would give us
 a performance boost on Solaris.

 The fact the compiler is more fussy, also tends to weed out some sort of
 bugs. On 't2' the Sun C compiler is

 {{{/opt/sunstudio12.1/bin/cc}}}

 and the C++ compiler is

 {{{/opt/sunstudio12.1/bin/CC}}}

 On the C++ compiler, you will probably need the option

 {{{
  -library=stlport4
 }}}

 as that will then implement the latest C++ standard. (The older C++
 standard is not compatible with the latest standard. For backwards
 compatibility Sun's C++ compiler defaults to the old C++ standard.}}}

 Previously I tried building lcalc with the Sun compiler but got lots of
 warnings and error messages. But if the code has been cleaned up, things
 have more chance of working.

 The point I made above about storing the exact (or least high precision)
 result in the test file, would be that is some record of what and should
 be, even though it is not going to be achieved.

 Then if you bring out a later version of lcalc, which deviates more from
 the exact result, people will at least know. It would only add 70 or so
 bytes to a file.

 Dave

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