|Interface between Parse Tree and translators firstname.lastname@example.org (1994-10-15)|
|Re: Interface between Parse Tree and translators email@example.com (1994-10-21)|
|Re: Interface between Parse Tree and translators firstname.lastname@example.org (1994-10-19)|
|Re: Interface between Parse Tree and translators email@example.com (1994-10-22)|
|From:||firstname.lastname@example.org (Venkateswara Rao)|
|Date:||Sat, 22 Oct 1994 12:49:09 GMT|
Thanks for all who responded to my query. I found that I have not presented
the problem well. Here is the description of the problem ( which I think is
1. The parser and parse tree should be made a separate "utility" ( to more
precise a DLL )
2. The client wants us to use VC++ 2.0/WinNT.
the language for which we are trying to build a compiler for, is sort of
intermediate language. All the above mentioned languages have "editor"
programs through which users enter their programs. When a save command is
issued, a translator to my language ( call it Neutral form Language) is
invoked thus creating NFL text. Now, the compiler of NFL ( our project )
is invoked to generate machine code of a PLC. The problem is for every
model of the PLC of my client our compiler has to generate code. As we
already have CodeGen functions for all models of PLCs. The question is how
do we design parse tree such that A DLL for the parser and parse tree
building can be built and using which we can build a compiler for each PLC.
Sorry for not communicating the problem correctly,
Return to the
Search the comp.compilers archives again.