#7377: Symbolic Ring to Maxima via EclObject
------------------------------------------------------------------------------------+
Reporter: nbruin
| Owner: nbruin
Type: enhancement
| Status: needs_work
Priority: major
| Milestone: sage-feature
Component: symbolics
| Keywords:
Author: Nils Bruin, Jean-Pierre Flori
| Upstream: N/A
Reviewer: Jean-Pierre Flori, François Bissey, Karl-Dieter Crisman
| Merged:
Work_issues: Maxima question doctests, 100% coverage, Maxima command list
doctest |
------------------------------------------------------------------------------------+
Changes (by kcrisman):
* work_issues: => Maxima question doctests, 100% coverage, Maxima
command list doctest
Old description:
> With maxima-as-an-ecl-library and ecl accessible as a library, we can
> start interfacing with maxima via a binary library interface. This should
> be more efficient and more robust, because expressions can be transmitted
> in a much richer format than text and parsing does not have to recognise
> error messages and questions (since communication does not go via
> STDIN/STDOUT anymore)
>
> ----
> Status: All doctest failures (8 in total across 4 files) are due to the
> fact that Maxima asking a question now triggers a different error.
>
> ----
> Applies cleanly to 4.6.2.
>
> This ticket is dependent on #10766, #10773, #10743. Ticket #10818 is
> desirable but not essential. Apply:
>
> {{{
> trac_7377-abstract-maxima_p2.patch
> trac_7377-maximalib_p2.patch
> trac_7377-fastcalculus_p2.patch
> trac_7377-better-ask-error_p2.patch
> trac_7377-split_and_refactor-p2.patch
> trac_7377-lazy-maxlib.p2.patch
> trac_7377-floatcast.patch
> trac_7377-unicode_to_ecl-p1.patch
> }}}
New description:
With maxima-as-an-ecl-library and ecl accessible as a library, we can
start interfacing with maxima via a binary library interface. This should
be more efficient and more robust, because expressions can be transmitted
in a much richer format than text and parsing does not have to recognise
error messages and questions (since communication does not go via
STDIN/STDOUT anymore)
----
Status: Nearly all doctest failures (8 in total across 4 files) are due to
the fact that Maxima asking a question now triggers a different error.
One comes from a change in the list of Maxima commands created in the new
interface.
----
Applies cleanly to 4.6.2.
This ticket is dependent on #10766, #10773, #10743. Ticket #10818 is
desirable but not essential. Apply:
{{{
trac_7377-abstract-maxima_p2.patch
trac_7377-maximalib_p2.patch
trac_7377-fastcalculus_p2.patch
trac_7377-better-ask-error_p2.patch
trac_7377-split_and_refactor-p2.patch
trac_7377-lazy-maxlib.p2.patch
trac_7377-floatcast.patch
trac_7377-unicode_to_ecl-p1.patch
}}}
* attachment:trac_7377-abstract-maxima_p2.patch
* attachment:trac_7377-maximalib_p2.patch
* attachment:trac_7377-fastcalculus_p2.patch
* attachment:trac_7377-better-ask-error_p2.patch
* attachment:trac_7377-split_and_refactor-p2.patch
* attachment:trac_7377-lazy-maxlib.p2.patch
* attachment:trac_7377-floatcast.patch
* attachment:trac_7377-unicode_to_ecl-p1.patch
--
Comment:
> * We could catch errors as suggested in the previous comment to report
them as before. It could be changed back to something else in a later
ticket (hopefully this ticket could be merged quickly, and anyway there is
still a lot of work left to communicate directly with Maxima as a lib
avoiding strings transformations).
Okay, that seems best to me as well so it can actually get merged.
Presumably lots of potential followup tickets.
So I will try to do this today on top of the current list of patches,
though I expect whatever I create will be merged by one of you into a p3
patch if that makes it easier to follow.
> * I'll try to add doctests this weekend.
Impressive! Hopefully at least some can be nearly copied from the previous
doctests (?)
> * As far as the problem mentionned in comment 106 is concerned, we
could mark its output as random or something like ![... ,gcd,...another
function,...] (and modify commands() later if really needed).
Probably better to have an actual doctest like that, as random might allow
weird things to slip through.
> Afterwards the ticket would finally be ready for review.
Yes!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7377#comment:109>
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.
