This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
Make error/warning numbers and message text more consistent with VBC #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and variable name to match the behavior of VBC.
…ultiple set/get methods.
…of single and multi-dimensional arrays.
rolfbjarne
added a commit
that referenced
this pull request
Oct 2, 2011
Make error/warning numbers and message text more consistent with VBC
|
Pretty much exactly as I would have done it myself, really good work. Thanks! |
This was referenced May 22, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changesets updates some of the existing errors that are issued when compiling invalid code to make the error numbers, message text and locations more consistent with the equivalent errors issued by VBC when compiling the same code.
When compiling some of the tests for invalid code like "#Const", VBNC was issuing bogus errors in the scanner after the first error so the changes to the "Next" method are there to try and improve error recovery and prevent these bogus errors from being issued.
All of the changes are covered by the addition of new tests to the test suite and successfully pass without introducing any new failures when running the regression tester.