Changeset 9059213 for src/Parser/parser.yy

Timestamp:

Oct 19, 2016, 10:32:04 PM (8 years ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

ADT, aaron-thesis, arm-eh, ast-experimental, cleanup-dtors, deferred_resn, demangler, enum, forall-pointer-decay, jacob/cs343-translation, jenkins-sandbox, master, new-ast, new-ast-unique-expr, new-env, no_list, persistent-indexer, pthread-emulation, qualifiedEnum, resolv-new, with_gc

Children:

315f634, fe7b281

Parents:

c2183a3

Message:

small changes to bring me up to date

File:

• src/Parser/parser.yy (modified) (5 diffs)

src/Parser/parser.yy

@@ -10 +10 @@
 // Created On       : Sat Sep  1 20:22:55 2001
 // Last Modified By : Peter A. Buhr
-// Last Modified On : Wed Oct  5 14:10:46 2016
-// Update Count     : 2002
+// Last Modified On : Wed Oct 19 22:19:33 2016
+// Update Count     : 2003
 //
 
@@ -278 +278 @@
 //
 // Cforall compounds this problem by introducing type names local to the scope of a declaration (for instance, those
-// introduced through "forall" qualifiers), and by introducing "type generators" -- parametrized types.  This latter
+// introduced through "forall" qualifiers), and by introducing "type generators" -- parameterized types.  This latter
 // type name creates a third class of identifiers that must be distinguished by the scanner.
 //
 // Since the scanner cannot distinguish among the different classes of identifiers without some context information, it
-// accesses a data structure (the TypedefTable) to allow classification of an identifier that it has just read.
-// Semantic actions during the parser update this data structure when the class of identifiers change.
+// accesses a data structure (TypedefTable) to allow classification of an identifier that it has just read.  Semantic
+// actions during the parser update this data structure when the class of identifiers change.
 //
 // Because the Cforall language is block-scoped, there is the possibility that an identifier can change its class in a
@@ -289 +289 @@
 // particular declaration, each declaration is itself a scope.  This requires distinguishing between type names that are
 // local to the current declaration scope and those that persist past the end of the declaration (i.e., names defined in
-// "typedef" or "type" declarations).
+// "typedef" or "otype" declarations).
 //
 // The non-terminals "push" and "pop" derive the empty string; their only use is to denote the opening and closing of
@@ -431 +431 @@
 field_name:
         no_attr_identifier
+                // x.1, x.[0, 0.0]
         | INTEGERconstant
         ;
@@ -2723 +2724 @@
         | multi_array_dimension type_specifier
                 { $$ = $2->addNewArray( $1 ); }
+
         | '[' ']' new_identifier_parameter_ptr
                 { $$ = $3->addNewArray( DeclarationNode::newArray( 0, 0, false ) ); }