Ilya Etingof

Expression tags that seem conceptually close to Apache config would probably be [ap_expr](https://httpd.apache.org/docs/2.4/expr.html). But these seem quite rigid in what they can do and httpd-specific. [jsp](https://www.javatpoint.com/jsp-expression-tag) and jinja expression tags...

It seems that it should be easy to parse stuff out of `` tag and just feed it to the jinja engine which would take care of the rest. But...

No, my config files do not happen to use expression tags of any kind. But I think I could try to add those for the greater good. Or you can...

One thing I do not quite get is your use-case... Do you need this parser to actually evaluate expression tags? Or just parse/dump them untouched? I wonder how reasonable would...

> Evaluating expressions gives users flexibility to generate dynamic configurations with less config lines. For example users can write loops or write conditional statements. Let me know if you think...

BTW, the parser in its current state can parse `ap_expr` expression tags. Just parse and dump, not evaluate. So I added a test case in commit 779fef8dc703a15644e6bf5ac9eeb02b564218db

The issue here is that closing `MYPYTHON` anchor is indented. I've modified the lexer to allow that (see commit 8a9f5b34bb1bd07e44fa94fb0b9b76181d37bb58). But now I am curious how would you include `MYPYTHON`...

Hmm, is it a good idea to allow whitespaces around the anchor? At least with bash, this is [not allowed](http://tldp.org/LDP/abs/html/here-docs.html#FTN.AEN17822).

It does, but I feel like this may break things elsewhere. May be we should better make this behavior configurable.

Hey, @sydneyli! Do you think this has been fixed lately?