Changes between Version 109 and Version 114 of Ticket #7377
- Timestamp:
- 03/14/11 16:07:54 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7377
-
Property
Work issues
changed from
Maxima question doctests, 100% coverage, Maxima command list doctest
to
-
Property
Work issues
changed from
-
Ticket #7377 – Description
v109 v114 1 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) 1 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). 2 2 3 ----4 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.5 6 ----7 3 Applies cleanly to 4.6.2. 8 4 … … 18 14 trac_7377-floatcast.patch 19 15 trac_7377-unicode_to_ecl-p1.patch 16 trac_7377-assumptions-p1.patch 17 trac_7377-doctests.patch 20 18 }}} 21 22 19 * attachment:trac_7377-abstract-maxima_p2.patch 23 20 * attachment:trac_7377-maximalib_p2.patch … … 28 25 * attachment:trac_7377-floatcast.patch 29 26 * attachment:trac_7377-unicode_to_ecl-p1.patch 27 * attachment:trac_7377-assumptions-p1.patch 28 * attachment:trac_7377-doctests.patch