more precisely, the following (the original was putting the new global
variable in the wrong place)
704a705
> static Obj ProtectFname;
727a729,731
> /* For some reason itanium GC seems unable to spot fname */
> ProtectFname = fname;
>
730a735,736
> ProtectFname = (Obj)0L;
>
1071a1078
>
1078a
> I am not an expert for that part of Sage. But I would expect the
> output "[]" *only* if it is certain that there is no solution. I
> interprete the ValueError in the sense of "sorry, I can't solve this
> equation, and I can't prove the absence of solutions either".
That is the hope, yes, thoug
See http://trac.sagemath.org/sage_trac/ticket/6515 for some reasons
why this isn't quite as easy to implement, unfortunately. That
doesn't mean it's hard, but to make it work in full generality
requires some trickery I haven't had time to think about. Also, the
reason for this is because Maxima e
OK, this patch appears to fix the problem, indeed.
Dima
2010/1/11 Stephen Linton :
> Try this patch for saveload.c:
>
> 708a709
>> static Obj ProtectFname;
> 727a729,731
>> /* For some reason itanium GC seems unable to spot fname */
>> ProtectFname = fname;
>>
> 730a735,736
>> ProtectFname =
