Skip to content
This repository was archived by the owner on Mar 8, 2020. It is now read-only.

Fix string literal escapes #115

Merged
merged 5 commits into from
Apr 17, 2019
Merged

Conversation

bzz
Copy link
Contributor

@bzz bzz commented Apr 16, 2019

Fixes #111 by padding a new unescapedValue node to StringLiteral in native driver.

It is acquired though JDT parser, follows escape sequence logic in Java and is used only in Semantic mode, similar to bblfsh/javascript-driver#81 (comment)

bzz added 5 commits April 16, 2019 01:11
Signed-off-by: Alexander Bezzubov <[email protected]>
Now native Java AST contains both
 - escapedValue
 - unescapedValue
obtained from JDT parser.

That is similar to what javasript driver does and
allows to avoid having language-spacific escape
sequence handling on the Go side that can be
different from Go one.

See bblfsh#111 (comment)
for details.

Signed-off-by: Alexander Bezzubov <[email protected]>
@bzz bzz requested review from creachadair and dennwc April 16, 2019 09:38
@bzz bzz self-assigned this Apr 16, 2019
@bzz bzz merged commit ee904c2 into bblfsh:master Apr 17, 2019
@bzz bzz deleted the fix-string-literal-escapes branch April 17, 2019 10:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

semantic: string literal escape sequence handing
3 participants