Interpreter still broken and AstNodes are always null

May 6, 2009 at 1:46 AM
Hey Roman,

great work on the new april 2009 version. I like the new project and all the refactoring you have done, it also makes some things easier to understand and to figure out whats going on.
You wrote in change set 24373 that the interpreter is broken and almost all my samples and unit tests use AstNodes (or as it is called now ParseTreeNode.AstNode), but those are always null because Grammar.CreateAstNode's implementation is commented out.

Any ideas when this will work again or how I can fix it maybe myself (just need the AstNodes to be the types I specify when creating NonTerminals and a way to execute DoEvaluate for all AstNodes).

May 6, 2009 at 4:33 AM
about AstNode creation - yeah, you're right, that shouldn't be commented. Interpreter is broken, but parser still can create AstNodes, whatever they are. 
 Just uncomment the body of method Grammar.CreateAstNode. But remember that nodes themselves should accomodate new IAstNodeInit interface for initialization. I will uncomment it soon, right now fixing other stuff, and not ready to upload
have fun!
May 6, 2009 at 1:44 PM
Okay, that sounds good, will try this evening. Should be easier than I thought. Yesterday I was still all confused about all the namespace and class name changes, new stuff like ParseTree.