Compilers - Browse information format

Author

Browse information format

jacob navia

2006-07-28, 10:00 pm

I am developing an IDE since a few years, and after many trials I
have settled for SQL databases for storing information about
the program.

The information I gather is
o type information
o coordinate information (precise line, file column of definition)
o identifier information
o macros definition

and several other stuff like usage tables, etc.

I wonder if anyone here knows of papers or references about this.

Are there any standards that would allow different IDEs to exchange
info?

I have now developed a bunch of SQL tables where the hierarchical
information is stored using "pointers" , i.e. a record can contain
a reference to the index of another record.

This is better than the ad hoc ascii files I had, but still quite messy.

Any ideas?

Thanks in advance for any info

jacob

Hans-Peter Diettrich

2006-07-29, 7:00 pm

jacob navia schrieb:

> I am developing an IDE since a few years, and after many trials I
> have settled for SQL databases for storing information about
> the program.
>
> The information I gather is
> o type information
> o coordinate information (precise line, file column of definition)
> o identifier information
> o macros definition
>
> and several other stuff like usage tables, etc.
>
> I wonder if anyone here knows of papers or references about this.

Have a look at the debug information, as stored in popular file formats
(ELF...). But most probably it will not include information about macros
(or types) :-(

> Are there any standards that would allow different IDEs to exchange
> info?

Look at popular open source IDEs, like Eclipse.

> I have now developed a bunch of SQL tables where the hierarchical
> information is stored using "pointers" , i.e. a record can contain
> a reference to the index of another record.

Here you may hit the limits of relational databases. For "proper"
references to local variables or other local symbols, you'll need
handles for the local scopes, in addition to the symbol names. Or you
can use synthetic names, which include an key for the scope of the
symbol. Possibly such names must be handled in dedicated code, outside
the database.

DoDi

Sponsored Links