|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:||Willy Jacobs <WN.Jacobs@net.HCC.nl>|
|Date:||16 May 1999 15:30:39 -0400|
|References:||99-04-120 99-05-031 99-05-033|
Mike Harrison wrote:
> Salvador V. Cavadini <email@example.com> 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:
> Snodgrass, Richard.
> The interface description language: Definition and use.
> Published 1989, by Computer Science Press.
> ISBN 0-7167-8198-0.
> 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.
The other one (CMU/Tartan) is described in:
J.R. Nestor, J.M. Newcomer, P. Giannini, D.L. Stone
IDL - The Language and Its Implementation
Prentice-Hall, 1990, ISBN 0-13-450214-0
An IDL-lite implementation as descibed in the book (Mini IDL) is
> Mike H.
Return to the
Search the comp.compilers archives again.