#10682: sum fails with lower bound != 0 or 1 (upgrade maxima to 5.26)
---------------------------------------------------------+------------------
   Reporter:  fmaltey                                    |          Owner:  
burcin                    
       Type:  defect                                     |         Status:  
needs_info                
   Priority:  critical                                   |      Milestone:  
sage-5.0                  
  Component:  symbolics                                  |       Keywords:  
maxima 5.26.0 binomial sum
Work_issues:  domain issue, error handling in nintegral  |       Upstream:  N/A 
                      
   Reviewer:  Jean-Pierre Flori,                         |         Author:  
Dima Pasechnick           
     Merged:                                             |   Dependencies:      
                      
---------------------------------------------------------+------------------

Comment(by dimpase):

 Replying to [comment:43 jpflori]:
 > I would rather follow Nils approach and at least include a try/finally
 statement in cas an error is raised.
 >
 > Doing so, we're sure not to let the domain set to real after leaving the
 function because of an error.
 >
 > Then, you'd better use "P" already present in the code rather than
 sage.calculus.calculs.maxima so that you're sure to use the same maxima as
 the one that will be used for solving the equation. Currently it's
 equivalent, but if something else changes in the future, such a choice
 will make everything easier.


 I really cannot imagine a scenario when one would run several instances of
 maxima in a totally uncoordinated way. If such a major change was ever to
 happen, surely a facility to execute a series of maxima commands in a
 given maxima instance would be available, and could be used then.


 >
 > Finally, on my side, I'd really prefer first to use the option approach
 you already implemented, and then to bakup the previous value of domain
 and set it back in the finally statement (rather than setting it to
 complex all the time).*

 That's a good point, regardless. As I said, when working on the previous
 patch I overlooked a way to set domain by another call to maxima.

 [...]

 > A last question is to know what we do when nintegral returns an error
 code.
 >
 > Do we let the situation as is? Or do we raise an error. I would agrre
 that this should be treated in another ticket, but I also don't think
 there is a better choice to make. Some discussion should happen.

 It surely can be handled better, but it surely should  happen on another
 ticket.

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