From: | Hans-Peter Diettrich <DrDiettrich1@aol.com> |
Newsgroups: | comp.programming,comp.compilers,comp.editors |
Date: | Fri, 08 Apr 2011 23:39:09 +0200 |
Organization: | Compilers Central |
References: | 11-04-009 |
Keywords: | tools, editor |
Posted-Date: | 10 Apr 2011 14:44:54 EDT |
HiramEgl schrieb:
> Therefore, I see all these elements as branches and leaves of a big
> tree-structure (the SOURCE-STRUCTURE).
Where do you want to start and stop building that tree?
To start you need kind of a project, that contains a number of source
modules, which then refer to other modules or interfaces, depending on
the source language; C uses #include for importing external
declarations, Pascal dialects have "uses" for the same purpose. How
shall your editor find the related files? In the case of C, where
shall your editor find the definitions, related to the imported
declarations? At least you'll need according parsers, for every
supported language and compiler.
Do you want to recurse down into every additional external
declaration, including all libraries used in the project? In the case
of Free Pascal this requires to add not only a compiler attribute and
related search pathes to the configuration, but also for the target
machine, OS and (Lazarus) widgetset.
Your approach looks nice, as soon as such a structure tree exists, but I
see the biggest problems just in the construction of that tree.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.