#14308: unwanted maxima verbose output
-------------------------------------+-------------------------------------
Reporter: zimmerma | Owner: was
Type: defect | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: Nils Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/maxima_verbose_output | 972427193788bc3f0c61951b063780772d55edfe
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nbruin):
Replying to [comment:11 kcrisman]:
> > > that error finally make me find the better routine in maxima to
execute maxima code [...]
> >
> > great!
>
> The only downside is that it now talks only about ECL and not Maxima,
which may be confusing for some folks. What do you think?
I'm not so keen on the ECL says -- Maxima says bit. It makes debugging
feel like marriage counselling. I only put that in when I was writing the
error catching and I wanted to confirm which code was catching/producing
the errors. We can of course regain this behaviour quite easily without
patching merror or writing the horrible shim we had before. If errcatch is
true then merror raises a very clearly marked condition (CL for exception)
so we could just catch that and raise another error with the "Maxima says"
thrown in. I'd rather stick to what maxima offers already, though.
> Amazingly, I personally am responsible for the
[http://trac.sagemath.org/attachment/ticket/7745/trac_7745-upgrade-
maxima.patch code] that catches this. Now that we have the lib etc.,
what do you think? I think it's still okay that we catch an error in
solve and just return that we can't do it, but in retrospect the way I did
it was just enough to get by.
I would normally think it's not a good idea to catch that error so broadly
-- you really only know *something* went wrong (and having Maxima in the
error message hardly improves that -- Checking the "ECL" is hardly more
generic). On the other hand, it's in solve. Those answers aren't
trustworthy if there's no error either.
--
Ticket URL: <http://trac.sagemath.org/ticket/14308#comment:13>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
