managing include files and boost::spirit::lex

Peter Foelsche <[email protected]>
Newsgroups gmane.comp.parsers.spirit.general
Message-ID <CANjPSNOm--zoeq3wUwmU_UzgZxtsDr30obv+R6fr1j3+HOXMTg@mail.gmail.com>
Am I going right with the assumption, that in order to deal with include
fiiles (and defines/macros) I should rather go with two lexers, with the
first one dealing with include files and defines and the second one doing
the real lexer work by reading the output from the first? I'm asking this,
since I'm confused about a iterator range, which is getting modified
dynamically -- first some position could match the first character after
the newline after the include statement and at some other time it could
match the first character of the included file. Since I don't know, if some
iterator has already been dereferenced and if I'm confusing the lexer by
dynamically modifying what some iterator is pointing too.

Peter

-- 
This email may contain material that is confidential and/or proprietary 
that the sender intended only for specific recipients. Any review by 
unintended recipients, forwarding or creating derivative works without the 
written permission of Silvaco, Inc <http://silvaco.com>. or its 
subsidiaries is strictly prohibited. If you are not the intended recipient, 
please contact the sender and delete all copies.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev

_______________________________________________
Spirit-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spirit-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.