[Cpptool-develop] About extracting symbol information

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
 <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello baptiste, 
 
Have you ever thought about moving the symbol extraction part also into
the grammar ? 
I've notice this idea on a parser-generator language and was wondering
if the same mechanism 
can help us to simplify the work of symboltable extraction. Currently
it's not so easy to synchronize 
the cpp_grammar.txt file and the "symboldeclarator.cpp" where symbol
extraction takes place. 
what about extending the grammar-syntax by keywords for symbol
extraction. Some examples: 
 
Entry-Point: 
translation_unit = :enterscope('translation-unit') :node(
'translation_unit', declaration_seq ) :leavescope; 
 
Declaring a class: 
 
class_head_name = :node( 'class_name', 
&nbsp;&nbsp;&nbsp; optional_alternative( :node('dll_macro', id ), 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ?( :node('nested_name_specifier',
nested_name_specifier) ) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [:node('id', id) | template_id] ) ); 
 
class_head = class_key ?( class_head_name ) ?( base_clause ); 
 
class_specifier = :node( 'class_specifier', class_head :declareSymbol('class',$subnode('class_name')
) 
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp; :enterscope('class-scope',
:subnode('class_name')) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; '{' ?( member_specification ) '}' 
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; &nbsp;&nbsp; :leavescope 
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ); 
 
New scope declaration extension: 
named_namespace_definition = 'namespace' id :push($2)
namespace_body :pop;&nbsp;&nbsp; &nbsp;&nbsp; ## $2 means second element which is
'id' 
 
namespace_body = '{' :enterscope($top) declaration_seq :leavescope
'}'; ## $top is the top element in element stack 
 
unnamed_namespace_definition = 'namespace' :push('&lt;&gt;')
namespace_body :pop; 
 
namespace_definition = :node( 'named_namespace_def',
named_namespace_definition ) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | :node( 'unnamed_namespace_def',
unnamed_namespace_definition ) 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; 
 
I'm not sure about that push/pop mechanism, but I think we need
something to propagate information across 
none-terminal-elements. 
 
:enterscope(&lt;string&gt;) 
:enterscope(&lt;scope-type&gt;,&lt;named-node&gt;) 
:leavescope 
:push(&lt;string&gt;) 
:push(&lt;number&gt;) 
:push(&lt;named-node&gt;) 
:pop 
:subnode(&lt;string&gt;) 
 
What do you think about this ? I haven't read through the
parser-code for grammar, so I don't know about the pit falls. 
 
greetings from 
Andr&eacute; 
 
</body>
</html>