From: Andre B. <and...@gm...> - 2002-12-19 20:31:30
|
I have just found the bug which causes the failing of the "testForScope" working with my parser extensions. It was a wrong property of the 'forIterationExpression' const ASTNodeType ASTNodeTypes::forIterationExpression( "for-iteration-expression", hasScope | mayHaveVariableDeclProperties | mayHaveLocalScopeIdentifierChildren | mayHaveScopeGeneratorProperties ); where "mayHaveLocalScopeIdentifierChildren" is really "mayHaveLocalScopeIdentifierProperties" since all elements of the forIterationExpressions are Properties. to see this bug optimistical - it helped me to get into the way how identier resolving is done ;-) btw) is there any idea how to solve this problem of VC6 ? since the vc6 does not open an extra scope for the "for-statement" and keeps it simply like a declaration within the scope of the for-statement. e.g. int i; for (int i; .... --> will lead to a compiler error "redefinition of 'i'", whereas this works in "stdc++" Should we add some configuration settings, so that for this case the scope creation will depend on compiler settings ? Ok, I'm ready to check in my changes, message me if i can. -- André |