From 86df359a97bffafd23fb3b11e47fb2ef979c37f2 Mon Sep 17 00:00:00 2001 From: Robin Jadoul Date: Sat, 28 May 2016 17:49:51 +0200 Subject: [PATCH] Add SyntaxHighlighter cmake rules mention to the readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5f47708..e771ff3 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ You can now simply run `./bin/Lexesis` with the arguments you like (see below an ## More examples More examples can be found in the *examples* subdirectory, go ahead an have a look at them. Feel free to play around and experiment with them. -The *keywords* example simply prints the lexed token type, along with its content, while the *SyntaxHighlighter* example is a bit more complete, making use of multiple lexers at once and providing a simple form of syntax highlighting for xml in the terminal using ansi escape codes. Be aware however that this also accepts anything that even remotely looks like xml, since the regular languages underlying the lexers cannot verify or parse xml. +The *keywords* example simply prints the lexed token type, along with its content, while the *SyntaxHighlighter* example is a bit more complete, making use of multiple lexers at once and providing a simple form of syntax highlighting for xml in the terminal using ansi escape codes. Be aware however that this also accepts anything that even remotely looks like xml, since the regular languages underlying the lexers cannot verify or parse xml. Additionally, the SyntaxHighlighter example also contains a couple of CMake rules that allow automatic generation and regeneration of lexer source files when the *.lxs* file changed. See the [CMakeLists.txt](examples/SyntaxHighlighter/src/CMakeLists.txt) if you are curious. ## Tested with | OS | Compiler | Boost version |