how to enable traces for Boost Regex and Boost Spirit Lex

Question

How can I enable debugging traces for those libraries such as the traces created by Boost Spirit Qi. It would be useful to get some generated XML files which show me the paths of the underlying states.

I think you know what you're looking for. It would be nice to just link to an example of what you meant, instead of "sketching a feature request" as if you just invented it. — sehe, Jun 18 '14 at 07:13

score 4 · Accepted Answer · edited May 23 '17 at 10:33

4

I don't think Boost Regex has this. See How do you debug a regex?

For Boost Spirit you can define

  #define BOOST_SPIRIT_DEBUG
  #define BOOST_SPIRIT_LEXERTL_DEBUG

and a similar one for Lex. The output for Lex is not XML, as I remember, but it does name the state transitions and (obviously) recognized token IDs.

For an example of how to use BOOST_SPIRIT_DEBUG_NODES see one of my answers

See also

Debugging (http://boost-spirit.com/home/articles/doc-addendum/debugging/)

edited May 23 '17 at 10:33

Community

1
1

answered Jun 18 '14 at 07:14

sehe

374,641
47
450
633

Do I have to use BOOST_SPIRIT_DEBUG_NODES for the token_def attributes like I did for the Qi rules? – Baradé Jun 21 '14 at 21:39
Not AFAIR. But I'd hunt down a sample that uses this to be sure – sehe Jun 21 '14 at 21:40

how to enable traces for Boost Regex and Boost Spirit Lex

1 Answers1