#10993: Update eclib to latest upstream release
-----------------------------------+----------------------------------------
       Reporter:  cremona          |         Owner:  cremona                    
     
           Type:  enhancement      |        Status:  needs_work                 
     
       Priority:  major            |     Milestone:  sage-5.0                   
     
      Component:  packages         |    Resolution:                             
     
       Keywords:  elliptic curves  |   Work issues:  ldconfig in spkg-install   
     
Report Upstream:  N/A              |     Reviewers:  Frithjof Schulze, Jeroen 
Demeyer
        Authors:  John Cremona     |     Merged in:                             
     
   Dependencies:  #11354           |      Stopgaps:                             
     
-----------------------------------+----------------------------------------

Comment (by leif):

 Replying to [comment:67 cremona]:
 > Replying to [comment:66 leif]:
 > > > Is the problem with that div function the only one on gcc-4.7?

 I just did a quick build on Ubuntu 10.04.4 LTS x86_64 with (my own build
 of) GCC 4.7.0, without setting any `CFLAGS` or `CXXFLAGS`; `make check`
 apparently passed without errors.

 Only noticed that eclib's `configure` apparently doesn't yet check whether
 the NTL and PARI installations passed to it really work; I used the ones
 of some Sage 5.0.beta10 installation I also compiled with GCC 4.7.0, but
 accidentally passed `--with-*=$SAGE_ROOT` instead of
 `--with-*=$SAGE_ROOT/local` in the first place.  While `configure`
 succeeded with that, the compilation of course later failed, because
 `<NTL/foo>` couldn't be included.

 There should IMHO also be a `--with-gmp=...` option.

 [[BR]]

 > > But it's in general a bad idea to put functions with such commonly
 used names into the global namespace; don't know whether eclib (meanwhile)
 uses namespaces at all...
 >
 > I also ran into this with my restrict() functions which had to be
 renamed.  No, eclib does not yet have its own namespaces.  One day....  I
 already see that in the code I call my div() functions mostly as ::div()
 because of some similar clash, but have not before had a complaint about
 the function declaration.  I can see the point behind your "bad idea"
 comment, but I have been happily using my div(int,int) and div(long,long)
 functions for over 20 years, so I got there first!

 Yeah, C++ didn't have namespaces (but neither templates) in 1990... ;-)

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