|How to store an AST firstname.lastname@example.org (Salvador V. Cavadini) (1999-04-30)|
|Re: How to store an AST email@example.com (Steve Mading) (1999-05-07)|
|Re: How to store an AST firstname.lastname@example.org (Dave Hanson) (1999-05-07)|
|Re: How to store an AST email@example.com (Mike Harrison) (1999-05-09)|
|Re: How to store an AST firstname.lastname@example.org (Nils M Holm) (1999-05-16)|
|Re: How to store an AST WN.Jacobs@net.HCC.nl (Willy Jacobs) (1999-05-16)|
|From:||Mike Harrison <email@example.com>|
|Date:||9 May 1999 16:02:20 -0400|
Salvador V. Cavadini <firstname.lastname@example.org> wrote
>> I'm programming a front-end for a tool and I need to store in disk the
>> AST produced by the parser. The rest of the tool will randomly access
>> the AST's nodes. I would be greatful if someone can recommend an
>> efficient way for store the AST.
Another reference worth looking at, is:
The interface description language: Definition and use.
Published 1989, by Computer Science Press.
This concerns a language called IDL (which is quite distinct from
another IDL which is connected in some way with Corba). This IDL
stands in the same relation to families of directed graphs as BNF does
to families of Strings; ie. it is a graph meta-language.
One of IDL's main claims to fame is that it was used to define DIANA,
the quasi-official intermediate representation for Ada(83).
I have used it to define ASTs and Intermediate Languages, together
with a toolset (originally produce at UNC) though as Rick Snodgrass
moved to Arizona in '88/89 I suspect it may be obtainable from there.
I have not recently been working in this field and my information may
be rather out of date.
The UNC implementation is not the only one, there was at least one
other, done at (or at least by people from) CMU, but I don't have
details of that.
Return to the
Search the comp.compilers archives again.