[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
solution parse #include directive
From: |
Vijayaraghavan Jagannathan |
Subject: |
solution parse #include directive |
Date: |
Wed, 24 Oct 2001 15:08:18 +0530 |
Thanx mathew, I will look into flex and try to solve the problem.
Thanx in advance.
JVRN.
----- Original Message -----
From: "Matthew Palmer" <address@hidden>
To: "Vijayaraghavan Jagannathan" <address@hidden>
Sent: Wednesday, October 24, 2001 2:55 PM
Subject: Re: Hi
> Two things:
>
> 1) Keep responses on list, it keeps the archives in order and lets other
> people participate in the discussion, and
>
> 2) Turn off the fscking HTML.
>
> On Wed, 24 Oct 2001, Vijayaraghavan Jagannathan wrote:
>
> > 1. A preliminary level parsing that parses only the #include section can
> > be written. It will identify the files. With this info, the files can
be
> > merged together. Thus a single source input file could be formed outside
> > the context of parsing functionality. The resultant source file can be
> > sent to the parse function.
> >
> > 2. Try Bison to parse a stream ! i.e. read all the files and form an
> > image of the syntax in the memory. This stream could then be passed to
> > the yyparse of bison. This is a bit difficult and working on it.
> > Moreover I am working on a GUI that will debug the source. Hence
streams
> > arent efficient way to handle it.
>
> Use flex, and it's marvellous ability to have multiple input sources going
> at once. In fact, I think the manual actually goes about 95% of the way
to
> solving your problem for you.
>
> If using flex is out of the question, then rewrite it's buffer switch
> functionality yourself.
>
> And get rid of the TOFU. Standard quoting was invented for a reason.
>
> > ----- Original Message -----
> > From: Matthew Palmer
> > To: Vijayaraghavan Jagannathan
> > Cc: Bison GNU Help
> > Sent: Wednesday, October 24, 2001 2:03 PM
> > Subject: Re: Hi
> >
> >
> > On Tue, 23 Oct 2001, Vijayaraghavan Jagannathan wrote:
> >
> > > Hi all, I have the following requirement. Can anyone suggest a
method by
> > > which this can be solved.
> >
> > Boy, this reeks of an assignment. Have you even attempted it
yourself?
>
>
> --
> -----------------------------------------------------------------------
> #include <disclaimer.h>
> Matthew Palmer
> address@hidden
>
>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- solution parse #include directive,
Vijayaraghavan Jagannathan <=