Displaying undefined names from an external symbol table

Hi Scott,

For that sort of thing I would probably piggyback on the parsing phase.  If you make an IParser-based class, you could wrap the Parse method of the real parser.  Call the real parser first and get its results.  Then examine the AST and look at things like strings and invocation sort of calls such as what you show there.  If you find a scenario that is invalid, you can have your IParseData implement IParseErrorProvider to support reporting of errors.  Check out the "User Interface Features / Adornment Features / Squiggle Lines" topic in the documentation for more on that and how to get the squiggles to display.

I agree with you that for the special string case, it's probably better to let strings be strings per the lexer and add special handling for those later on.

Hi,

Thanks for the advice. I have overridden the Parse() function, but I notice that AST appears to be periodically set to null. If the AST is null, I can't check the arguments to generate the semantic parse errors. Wouldn't this mean that the squiggles under an undefined name would flash on and off? If so, can you suggest a solution?

Thanks again,

Scott

P.S. Very nice job on this control. It has been remarkably easy to get some pretty impressive capabilities added to my application.

Hi Scott,

Yes the AST being null would be a problem, but in those cases I suspect it is a problem with your parser where perhaps if there is a syntax error in the document, it's not recovering properly to at least return something in the AST.  If you are using our LL(*) Parser Framework, make sure you read through the sections on error handling and recovery.  Those are all key concepts to handle when using a parser with an editor since probably most of the time, an editor's text will be in an invalid state as the user is typing.