antlr is losing information

[emberian]

See http://stackoverflow.com/questions/24747360/distinguishing-literal-n-vs-embedded-newline. Until there is a resolution to this, the lexer verification is ignoring the contents every token that carries data :(

[steveklabnik]

traige: no changes that i'm aware of

[nagisa]

While we still have ANTLR grammar in tree, it is outdated and we predominantly rely on the other one we have in tree. Perhaps we should just remove ANTLR one now?

[emberian]

The ANTLR grammar was originally intended to be "pure" in the sense that it uses only language description and no code in its operation, and could easily be lifted into some formalism. This is quite at odds with how the flex and bison files operate.

[steveklabnik]

I would be okay removing ANTLR.

On Mar 17, 2016, 05:47 -0400, cmrnotifications@github.com, wrote:

The ANTLR grammar was originally intended to be "pure" in the sense that it uses only language description and no code in its operation, and could easily be lifted into some formalism. This is quite at odds with how the flex and bison files operate.

—
You are receiving this because you commented.
Reply to this email directly orview it on GitHub(#15677 (comment))

[Mark-Simulacrum]

ANTLR grammar is still in-tree. There is now an answer to the SO question, though, so perhaps that's significant to this discussion? It's possible the easiest answer here is to simply remove the ANTLR grammar from in-tree, possibly moving it elsewhere.

[steveklabnik]

Agreed; I'd be happy to just remove it. We're not planning on doing anything with ANTLR in the future that I know of, and if we need it, we can pull it back out of the history.