How to get ReportError to register an error when the AST node already has one

Hi Andrew,

Yes that functionality is by design.  It only reports the first parse error that is reported for an offset.  If we didn't have that, then a single typing mistake could trigger a lot of parse errors at the same offset and the list of those parse errors to the end user would lose its effectiveness due to there being so many.  Visual Studio also only shows the first one.

The functionality that does that is built into the core ParserState.ReportError method.  Would you like us to add an optional parameter to the ReportError(IParseError) method that says whether to overwrite any existing parse error at the same offset?

Hello,

I understand that it is by design, and i do not want to log multiple errors to a given AST node, so recording only the first logged error is fine by me. What I am having trouble with is that once a warning, i.e. not an error, has been logged, then a subsequent error will effectively be ignored, which is bad for the reason I explained in my earlier post. The functionality I would like is that an error overwrites a warning, as it is more important, but warnings should not overwrite errors, as they are less improtant. You could apply a simliar precedence-type logic with warnings and messages too.

I hope I've made myself clear and am not being unreasinable in my request. An optional parameter would be a solution of sorts, as it would allow me to decide my own precedence for diagnostics (I prefer not to call them errors, as I log warnings too) based in the ParseErrorLevel passed.

For some reason, the Reply button in your reply didn't work, hence the additional comment rather than a direct reply.

Hi Andrew,

Ok the priority idea sounds good.  Can you please write our support address and reference this thread?  We'll send you a preview build with the code update to test and make sure it's working properly for your scenario.