Context Navigation

Changes between Version 1 and Version 2 of Ticket #15902, comment 1

v1	v2
18	18	When I wrote this, it was really with the idea that it would be an error of the calculus library if maxima were fed a syntax error. Nearly all the translation between sage and maxima can be done on a deeper level than string back-and-forth parsing. See `sr_to_max` and `max_to_sr` and how they are used in `sr_integral`, `sr_limit` and `sr_sum`. It was originally the idea that the calculus-to-maxima_lib interface would eventually almost do away completely with string passing. As it turned out, this hasn't been such a priority.
19	19
20		In my opinion, `symbolic_expression_from_maxima_string` should only receive strings that parse in maxima. ~~Those are the ones that give the incomprehensible error message~~. Actual runtime errors are caught in a meaningful way:
	20	In my opinion, `symbolic_expression_from_maxima_string` should only receive strings that parse in maxima. Only the ones that don't give the incomprehensible error messages. Actual runtime errors are caught in a meaningful way:
21	21	{{{
22	22	sage: sage.calculus.calculus.symbolic_expression_from_maxima_string("1/0")