This is not a question, but for the Intel Fortran compiler documenters, if they read this post:
There are several typos that I see on this page that, to my understanding, require correction:
1. The article is about co_sum, but the declaration states: CALL CO_MAX
2. "...procedure is references..." should be "...procedure is referenced..." in the example.
3. There might be more typos, but these are the two that came immediately to my attention.
and as always, thanks for the impressive Fortran compiler, extensive documentation, and above all, making it freely available to all with the newest release.
A somewhat similar documentation error, this one on line 33 of the output from ifx /help on Windows:
2. Intel Fortran compiler options may be placed in your ifort -qnextgen.cfg file.
I suspect that a hasty global replace caused ifort.cfg to change to ifort -qnextgen.cfg.
Now that we have two compilers, ifort and ifx, please clarify whether the configuration files ifort.cfg and icl.cfg are shared by the classic and OneAPI compilers. Similarly, is there an environment variable IFXCFG pointing to the CFG file for ifx just as IFORTCFG points to the CFG file for ifort? The new compiler does not seem to read the configuration file of the ifort compiler, since the ifort.cfg file is in a subdirectory of the bin directory, and IFX.EXE is in the bin directory itself.
1. the ifort.cfg are all empty files - you find them with the fileseek but they do not show up as hidden files of zero size.
2. I removed all of the if compilers, I only installed the oneAPI and yet the files for the Parallel Fortran old are back on IntelSW - did I miss something?
[quote=JohnNichols]the ifort.cfg are all empty files[/quote]
The empty files are place holders. Users who compile in a command window can conveniently place their regularly used compiler options into those files, and avoid typing those options every time that they use the compiler from the command line.
See the section Using Configuration Files in the Ifort documentation.
Intel Fortran has provided this facility (and an associated environment variable, IFORTCFG) from at least version 4 (early 2000s). Digital Visual Fortran had an environment variable (DF) that you could directly set to a string of compiler options.
@JohnNichols , I also installed on a clean NUC. I am not sure what you are looking for. You should have a folder C:\Program Files (x86)\IntelSWTools\ide_support_2020 with FEE and VS16 subfolders.
Hmm - I need to investigate how to install .vsix files. That may be all that is needed to resolve integration issues. (Edit: "Open it using
VSIXInstaller.exe found inside
Common7/IDE in your Visual Studio installation.")