On Sunday, January 29, 2023 at 6:58:26 AM UTC-5, Sergey Budaev wrote:
> .. On Windows this may be a
> problem for ifort, I guess.
> ..
Note the problem for @Lynn McGuire is almost entirely @Lynn McGuire's code which is highly nonstandard per any of Fortran (and earlier FORTRAN version) standards and not portable and likely has a host of other questionable aspects and issues. Like most nonquality craftspeople, @Lynn McGuire then proceeds to blame the tools ..
Otherwise, as a company like WinSim Inc. that strives to sell software and services to chemical processing and related industries whose market capitalization is a trillion plus US$, with just a bit of discipline and humility and purpose and enterprise, any running code in earlier dialects of FORTRAN, even if billions of lines let alone the piddly millions LOC mentioned often by @Lynn McGuire, can readily be modernized to work with Microsoft Visual Studio 2022 and Intel Fortran 2023 in conjunction with Microsoft C/C++ compiler 2022 and also benefit from *graphical debugging* as well as making use of Fortran 2018 standard and C++20 standard along with some C++23 features. The competitors of WinSim Inc. are already using Visual Studio IDE successfully on Windows OS with Intel Fortran, Microsoft C/C++ compiler, etc.
And the bulk of the computations toward chemical process modeling and simulations, especially the most important aspects of thermophysical property and phase equilibrium computations using equation-of-state and activity coefficient models and other thermodynamic number-crunching can all remain in modern Fortran where they are best suited. Whereas many of the graphical user interface (UI), data processing, and other aspects can make use of a host of languages and platforms including C++, C#/VB, Python, etc. and also Fortran.
A teeny tiny flavor of what is possible on Windows OS with Intel Fortran 2023 compiler version supporting all of Fortran 2018 and Microsoft C/C++ compiler supporting C++20 (and C++23) features can be seen in this example I posted at the Fortran Discourse site on how to consume "a string of arrays" in Fortran in C++:
https://fortran-lang.discourse.group/t/return-an-array-of-strings-from-fortran-to-c/5100/7?u=fortranfan
Surely there are some problems with Intel Fortran integration with Microsoft Visual Studio in that there can be many initial missteps during installation and that the support for Fortran is *without all the creature comfort** that the users of Microsoft's own C# (and Visual Basic) languages receive. Plus there are some outstanding bugs Intel has not fixed now for close to 10 years. But these issues can be worked around, the benefits to be gained with a good build system for Windows and also graphical debugging are huuuge.
Again, the problem for @Lynn McGuire is almost entirely @Lynn McGuire's code ..