![]() (Sorry for the text not being too polished, I needed to write this quickly, but wanted to reply before the notification gets lost in time.) If Intel (or anyone else) supplied this, that would be a huge win. I tried running a fortran executable under a C++ debug configuration in vscode and if I remember correctly, one can see a list of the appropriate variables, it’s just the debugger doesn’t know how to display the content of any of the Fortran types. There’s little missing from having a usable debugger for vscode, IMO. If I had the option, I would leave VS instantly and would rarely look back. It’s fiddly process, but much faster than putting up with the constant annoyances of VS while trying to think about the code I want to write. My current workflow is I usually rather use vscode to write new code or refactor old one, and only use VS to build and debug. In vscode, one can at least use fortran-language-server, which is still work in progress and buggy (it’s basically a one man job AFAIK), but is orders of magnitude better than what Intel provides.Īll in all, I end up having to restart VS several times on an average day. It provides virtually no useful hints, the only one I’ve noticed is use modulename. the supplied IntelliSense for Fortran is useless.I very much prefer Makefiles and I would migrate to them instantly if I had the choice. The names of the options have no hint as to what they actually generate in the command line, you have to guess or search for each of the names in the manual to find out.Īll of this is completely redundant just to please Microsoft people who thought everything needs to fit in a GUI. You have to go through a graphical interface and click through 20 different sections to find your options. There’s no way to just type a list of command line switches you want to pass to the compiler. the UI for configuring projects is annoying and makes making mistakes easy. ![]() This has been happening on all the machines we have on all the versions of Intel Fortran we’ve had. after several hours of usage, the editor gradually slows down to a snail’s pace for fortran files, to the point where the letters you type appear several seconds after you press the keys.Writes something like “Operation didn’t succeed” to output, nothing more. ifort randomly stops building for an unknown reason.The problems I run into on a daily basis are: We have a solution containing about 15 projects (some executables, some libraries. We’ve been using Intel Fortran in our company to build a small FEM solver + a set of libraries for about 10 years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |