If you did not explicitly open unit 2 and gave it a name.fortran will create a default file name along the lines of fort2 or something like that. I understand it looks the same, but the issue here was a specific problem that Confluence Cloud was having at the time of the first post. If you are on unix/linux (which is likely), then just redirect the output to a file: a.out > myoutputfile.
I believe this is the problem youre experiencing. Your other option is to simply write to stdout (unit) and the redirect the output from the command line (eg: myfortranprogram > output.txt).
#Problem saving file simply fortran code#
for files, it will assume the file is F77 source code and use fixed formatting rules.
#Problem saving file simply fortran free#
f90 files, it will assume its working with FORTRAN 90 source code and use free formatting rules. These functions have never been part of any Fortran standard, and there is not universal agreement on their spelling. You can use another IDE if you do not like Visual Studio, or simply use Nmake. Inspect the directory one more time and see if an additional file appeared. GFORTRAN guesses the source code formatting based on the file extension. Only some combinations of Visual Studio and Intel Fortran are supported. To be sure, clean up the directory as much as possible to have only the files that you need to run the program.the executable itself and possibly an input file. If you are in Linux, make sure to list ALL files in the directory, even the ones typically hidden (.*)
THEN, run the program by typing its name at the prompt. To correct this situation, open a terminal and change directory to the directory where you actually have the executable. If you double-click on it, the OS may be launching a separate terminal/dos window with its own environment and default working directory, etc.so, it may be running your program in some other directory and not the one you think.
0 kommentar(er)
