![]() You know very well as a user that is wholly inadequate - one needs top-notch compiler, debugger and IDE/editor to be functional - but Intel management may not oblige. Resources toward IFX compiler only might be the extent of Fortran support Intel is willing to expend. On the other hand, the users often have to deal with painful regression as Microsoft issues new Visual Studio versions and features that worked before stop working and it takes years before something that worked in the debugger way back in 1998 starts to work again when reported to Intel support circa 2020. My management, for example, has noticed no improvement at all with Intel Fortran integration with Visual Studio IDE since 2008 and they are really angry and upset. There are definitely features missing from Modern Fortran and fortls that would make our lives a lot easier if present, but at the end of the day it is a matter of available free time and, I have posted my support and comments at the Intel forum.Ĭhances are rather high that when it really comes down to it, you may find Intel Software management is uninterested in any allocating additional resources beyond that needed for the most rudimentary support toward maintaining the Intel Fortran integration with Visual Studio which is what has been the case for nearly a dozen years now. So the issue boils down to the last comment by WardenGnaw I recall an issue being raised by a user in the Modern Fortran repo, which was forwarded to the vscode-cpptools team. My guess is that the debugger on Windows + ifort are not fully working. Arrays can be visualised in both watch windows and hover just fineĪlso not sure about this one, these are the default extensions for Free Form Fortran and of course you can associate more from the settings "extensions": [ I am afraid I do not quite understand this one. See my discussion with the vscode-cpptools team for more.Īrrays (one of the most important features of Fortran), however, cannot be viewed. some%foo%bar, hovering over foo will yield nothing ![]() This works relatively well for the most part, but there are some issues with hovering over custom type variables e.g. The “debug extension” is actually not a trivial task not only do you need the VS Code extension but you also need to create an implementation of the Debug Adapter Protocol (DAP) for Fortran.Ĭurrently how the debugger in VS Code works is that it piggybacks on the DAP servers from C++, which are proprietary, to provide debugging. The post raises some interesting problems but I think there are solution for most of the problems mentioned, with an exception probably being ifort + Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |