-
-
Notifications
You must be signed in to change notification settings - Fork 35
Added debugging functionality. #150
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
Added debugging functionality. #150
Conversation
I guess this branch should be merged to master after the dependabot PRs. |
Hi @gnikit and thanks for contributing. |
As stated in issue #9037 in github.com/microsoft/vscode is the way to go. Fortran does not do anything different from the inhouse C++ debugger, hence we should only have the extension allow breaking points and nothing else. This of course means that we will be depending on Microsoft's C++ extension for the debugger.
So I think this is done, I updated the README, I also updated the way we define the debugger, there is no need to specify the type of the debugger However, I feel that I should mention this to make things clear. I personally don't think that is an issue, but given how this is your extension I feel that I should let you know. |
### Check List - Highlight - [x] `select` keyword - *Merge #165 to fix #149* - [x] `rank` keyword - *Merge #165* - [x] `forall` keyword - *Merge #170 to fix #169* - Symbol List - [x] Symbols bug in VSCode +1.40 - *Merge #161 to fix #154* - [x] Symbols classification - *Merge #141 to fix #140* - [x] Long named symbols - *Merge #151* - Settings - [x] Add more options - *Merge #152* - Dependencies - [x] Merge `dependabot` PR's - [x] lodash - *Merge #144* - [x] mixin-deep - *Merge #146* - [x] handlebars - *Merge #155* - Code Completion - [x] Array constructor - *Fix #148* - New Features - [x] Breakpoints - *Merge #150*
Hi,
Not having the option to add breaking points for debugging has been bothering me for quite some time and I think it is unreasonable to have to install a completely new extension about this, so I took the liberty of adding them in the extension.
The implemented changes are trivial overall.