You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#... more stuff before
Match line_term at loc 20(1,21)
#multi word comment
^
Matched line_term -> ['\n']
Matched comment -> ['#multi word comment ', '\n']
Matched value -> ['#multi word comment ', '\n']
Match value at loc 21(2,1)
val3
^
Match string at loc 21(2,1)
val3
^
Match line_term at loc 24(2,4)
val3
^
Match line_term failed, ParseException raised: Expected '\r', found 'val2' (at char 25), (line:2, col:5)
Matched string -> ['val']
Matched value -> ['val']
Match value at loc 24(2,4)
val3
^
Match string at loc 25(2,5)
val3
^
Match line_term at loc 29(2,9)
val3
^
Matched line_term -> ['\r']
Matched string -> ['val2', '\r']
Matched value -> ['val2', '\r']
#... more stuff after
The text was updated successfully, but these errors were encountered:
Interesting issue. Could you also please supply a small sample string I can use for s? Probably past the repr of the string so that the control characters show up properly.
Having a
\r
in a string which is being parsed resets the output string in the debug output, overwriting what was already there.The parsing is correct, just the explanatory text is wrong.
\r
is imprtant as a standalone character, as I need to be able to accept it as a line terminator.results in (in part):
The text was updated successfully, but these errors were encountered: