backslashes break gore's scanner

[samertm]

gore> h\ello<enter>
..... <enter>
..... <ctrl-d>
gore> hello\t<enter>
..... <enter>
..... <ctrl-d>
gore> he\\llo<enter>
..... <enter>
.....

Only a couple escape sequences are valid: https://golang.org/ref/spec#Rune_literals

[motemen]

It's because gore enters line-continuation mode if it fails to parse input. What is your expected behavior?

As you may already know, for string literals you must surround them by "s:

gore> "hello\t"
"hello\t"

[samertm]

It's because gore enters line-continuation mode if it fails to parse input. What is your expected behavior?

That explains it :P I was expecting an error.

[motemen]

Got the point. I have currently no idea with this problem.

[samertm]

The reason I ask is because I'm writing a CLI app too, and I wanted to see how you handle backslashes. For my app, all backslashes outside of quotes are literals, and backslashes within quotes always escape the character after, which you can see here. Where do you parse CLI input? I'd like to take a look.

[motemen]

One night passed and I think we can use go/scanner to detect illegal characters in the source, though I have not tested it.

FYI, I'm parsing input using go/parser.ParseFile here and if the error was go/scanner.ErrorList, gore prompts to continue line here.

[itchyny]

This issue is resolved now.