I have an old Intel Fortran Compiler that is no longer supported (v 10 Standard on DVD) but works fine for maintaining some legacy codes that I still occasionally use.
I've never quite understood the rules for derived type component alignment requirements as it pertains to binary/stream IO of derived types. When if ever are padding bytes included in the write of
I've stumbled across a very interesting side-effect of the optimizer when compiling between -O0 and -O2 (there are some other flags, which I'll get to below). First, my code:
So i have this piece of code:
Is there any way to alter fortran compiler options by file extension? For example, I may want to enable more diagnostic checking on files that end with .f90 compared to those that end with .for.
License checkout for 2016 and newer product versions is very slow compared to the 2015 version on machines with remote access to the floating license server.
I read through all to posts on this subject and read that I have to compile the modules explictily before I compile the rest.
Is there a problem with this prototype in user32.f90? The MS documentation indicate that the function name includes an s after the word part "window", but this prototype does not. I'm getting a l
In this thread I'll add links to new Doctor Fortran posts. I'd like to keep the thread free of questions and comments - start a new thread, or add a comment to a post if you think it appropriate.