#17778: preparse behaviour
-------------------------+-------------------------------------------------
Reporter: | Owner:
mantepse | Status: needs_info
Type: | Milestone: sage-6.5
enhancement | Resolution:
Priority: minor | Merged in:
Component: user | Reviewers:
interface | Work issues:
Keywords: | Commit:
preparser | 44e5bb0b3f5026234edc375940e41ecf73579bdb
Authors: | Stopgaps:
Travis Scrimshaw |
Report Upstream: N/A |
Branch: |
public/17778 |
Dependencies: |
-------------------------+-------------------------------------------------
Changes (by tscrim):
* status: needs_review => needs_info
Comment:
Okay, so it does things a little differently than I thought. The
interpreter decides whether or not it needs to preparse a line. So the
interpreter keeps track of whether you're in a comment or not. If it has a
line break with a `\`, then it stitches the lines together. If it has a
parenthesis with a line break, then it feeds that (with the `\n`) into the
preparser as single string.
Although I can break the preparser by doing
{{{
sage: def foo(x):
....: R.<x> = QQ[
....: ]
}}}
So there is an issue with bad user input, but I'm not sure what to do
about that.
--
Ticket URL: <http://trac.sagemath.org/ticket/17778#comment:8>
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.
