Re: An interesting Parser problem

"sachin.goyal.new@gmail.com" <sachin.goyal.new@gmail.com> writes:


> We are planning to make an intelligent text editor (Why is not
> important, we have to do it.) ...


> So the first issue is to find the offset of each token in lex (yacc ?)
> This should also handle if some include file construct like "include
> abc.xyz" is encountered. In such a case, filename and offset from new
> file should be returned. Is there any other tricky case possible ?


If you have a macro pre-processor in your language, then you have one
additional tricky case which is text coming from macros.


Well, if you support #line style directives, you get yet another
tricky case, but for what you are doing, you might be able to handle
#line's by ignoring them.


Hope this helps,
-Chris


*****************************************************************************
Chris Clark Internet : compres@world.std.com
Compiler Resources, Inc. Web Site : http://world.std.com/~compres
23 Bailey Rd voice : (508) 435-5016
Berlin, MA 01503 USA fax : (978) 838-0263 (24 hours)
[In 1981 some friends of mine at Yale were working on syntax editors
and came to the conclusion that you did better with pattern matching
than trying to parse source code in an editor. I'm not sure anything
important has changed since then. It's "Z - the 95% program editor"
published in SIGPLAN Notices in 1981. If you have an online
subscription to the ACM digital library, you can download it. -John]

Return to the comp.compilers page.
Search the comp.compilers archives again.