@gnikit brillant work!!
I went a bit ahead and activated the pre-release version 3.4.2023020701 just for curiosity and while hovering in @jacobwilliams 's json-fortran saw several warnings or potential errors. Nontheless, the compilation has no issues. Changes in the reference norm maybe?
From the looks of it this has to do with function overloading. fortls does not do a great job with overloadded functions at the time. I have added an annotation to the GitHub issue: see Overloaded functions · Issue #6 · fortran-lang/fortls · GitHub
and I will have a more detailed look in the coming days.
If it is indeed due to overloading there is not much you can do, other than exclude the directories from the language server’s source paths.
Hi there, I’m using the extensions “FORTRAN IntelliSense” and “Fortran Breakpoint Support” for intellisense and code debugging. I see that these should be deprecated with the latest release, but I when I disable them, I lose both functions.
Disabling “FORTRAN IntelliSense” leads to loss of many intellisense features like “go to definition”, “mouse over to see variable declaration” etc.
Disabling “Fortran Breakpoint Support” leads to an error message from vs code saying that debug type ‘cppdbg’ is not supported.