Discussion Overview
The discussion revolves around the issue of gfortran not printing output in the command window when executed in Cygwin. Participants explore the behavior of output commands in different execution contexts and seek to understand the underlying reasons for the observed behavior.
Discussion Character
- Technical explanation, Debate/contested
Main Points Raised
- One participant notes that using WRITE(6,*) or PRINT(6,*) does not produce any output in the command window during execution.
- Another participant questions whether the command window remains open after execution or closes immediately, suggesting that the latter might require a command to pause execution.
- A participant observes that executing the program with ./a.exe results in printed output, while using the command run a.exe does not, prompting curiosity about the difference between these commands.
- One participant speculates that the run command may open a new shell, causing the output to be displayed in a different process than the one where the command was entered, unlike the direct execution of a.exe.
Areas of Agreement / Disagreement
Participants express differing views on the behavior of output in Cygwin, with no consensus reached regarding the exact cause of the issue or the differences between the execution methods.
Contextual Notes
Some assumptions about the behavior of command execution in Cygwin and the handling of output may be missing, and the discussion does not resolve the technical details of process management in this environment.