[LLVMdev] Symbol table for complex data structure

[James Molloy]

Hi,

As far as encapsulation is concerned, that's your decision (and sticking
the Symtab in a separate class is a good idea). I was more checking that
this symbol analysis is being done *on* your AST - so at the AST phase
of compilation.

James

> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of leledumbo
> Sent: 01 November 2010 10:17
> To: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Symbol table for complex data structure
> 
> 
> > The symbol table (in an AST, I assume?) deals with *symbols*.
> Assuming
> > your complex datatype is called a "struct" for simplicity's sake,
> your
> > symbol table would normally just store the struct's name, along with
> its
> > AST node.
> 
> Actually, I don't put it along with the AST. It's a separate class in
> separate module, should it be integrated?
> Hmm... storing the AST node might be a good idea, I was duplicating
the
> information by copying the declaration line, type, etc. as the symbol
> table
> entry. This is the point where I got confused in complex data type.
> --
> View this message in context: http://old.nabble.com/Symbol-table-for-
> complex-data-structure-tp30103380p30103564.html
> Sent from the LLVM - Dev mailing list archive at Nabble.com.
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-- 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.