#11542: Fix preparse_file to prevent constants from being assigned to
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner: was
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: user interface | Resolution:
Keywords: | Merged in:
Authors: Martin von Gagern | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/gagern/ticket/11542 | c8375cad159f50605c07da1447afc0ff1f6607b1
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by gagern):
Replying to [comment:17 nbruin].
Thanks for the feedback. The situation is the following: we see an
exception for *any* kind of syntax error, and the exception itself will
likely contain code snippets describing its location, but these code
snippets are neither for the code the user entered, nor for the code which
will eventually get executed, but instead contains some dummy values in
place of literals.
Perhaps I should do the following: try to parse the code with the actual
values plugged back in, and if that throws, let the exception escape. If
not, raise a new exception about there (probably?) being an assignment to
a literal. Will write code for that soon.
--
Ticket URL: <http://trac.sagemath.org/ticket/11542#comment:18>
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.
