-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Pull Request] Regex logic to handle errors and warnings displayed on console #53
Comments
Associated update complete |
There were a lot of changes in NppExec during this month, and I believe now the plugin is in a release candidate state. Do you have any changes to the regular expressions used by this filter? |
By the way, I've made some performance tests to understand why the all-in-one compilation script (that you initially created) requires noticeable time to be executed.
If you execute it as is, it is lightning-fast, it shows "GOTO was performed more than 10000 times" almost immediately. This is the performance of the CScriptEngine itself. Now, let's close NppExec's Console and modify this script:
This second version prints "GOTO: 1" to a hidden RichEdit window 10000 times. You might think that a hidden RichEdit window should not take much time to repaint itself while adding these lines, but in reality this version takes much longer than the previous one! This is the performance of the CScriptEngine plus Rich Edit control. I also did some profiling using Visual Studio - and most of the time is indeed spent within the Rich Edit control!
|
I created pull request #51, to add the Regex logic.
I tested it on 18 languages by creating Hello World source files with errors.
If you like to test it, I have the source file in this zip file. BadHelloWorld.zip
I used the following NppExec script to test each file:
Let me know if you have any questions.
The text was updated successfully, but these errors were encountered: