I spent last few days digging around why would such an innocently looking feature be left as a TODO. I was looking for something to put my hands into, and it looked promising enough.
Turns out ANTLR doesn't support back-references or forward-references at all. There is no good way to do it using only it.
A known workaround is to embed actions that verify whether the two tokens match (analogous to how XML opening-closing tag pair match tagname), but those actions involve putting a piece of code inside the grammar lexer definition in a programming language that matches the language of the generated lexer.
That would mean putting Java code in concise-encoding grammar definitions, and thus tying it tightly to Java.
I want to write a Rust 100% implementation. AFAIK at this moment I need to write a custom lexer and parser to make verbatim escape sequences work.
TLDR; ANTLR is insufficient, because VES grammar is context-sensitive
I spent last few days digging around why would such an innocently looking feature be left as a TODO. I was looking for something to put my hands into, and it looked promising enough.
Turns out ANTLR doesn't support back-references or forward-references at all. There is no good way to do it using only it.
A known workaround is to embed actions that verify whether the two tokens match (analogous to how XML opening-closing tag pair match tagname), but those actions involve putting a piece of code inside the grammar lexer definition in a programming language that matches the language of the generated lexer.
That would mean putting Java code in
concise-encodinggrammar definitions, and thus tying it tightly to Java.I want to write a Rust 100% implementation. AFAIK at this moment I need to write a custom lexer and parser to make verbatim escape sequences work.
TLDR; ANTLR is insufficient, because VES grammar is context-sensitive