force write in Gfortran

[Richard E Maine]

On Mar 24, 2006, at 11:53 AM, Janne Blomqvist wrote:

> On Fri, Mar 24, 2006 at 02:03:48PM -0300, Paulo Ziemer wrote:
>> This happens only when several files are linked to forme one
>> executable. If the executable is created just from my "test.for"
>> everthing goes ok and all the string are correctely written.
>
> ?? I don't see how that could happen, but then I've been wrong before
> too. Perhaps, there is code in the rest of the program that closes
> and/or reopens the unit with different flags?

Or any other bug elsewhere in the code. That's my first reaction -  
that this sounds more like a program bug than a gfortran issue.  
That's common for things that work fine in small test cases, but fail  
in someone's large application. Might not be that, but the original  
posting sure doesn't have enough data to say much else useful. The OP  
didn't mention whether the program crashed or finished normally; it  
can make quite a big difference if the issue relates to flushing  
buffers.

-- 
Richard Maine                |  Good judgment comes from experience;
Richard.Maine@nasa.gov       |  experience comes from bad judgment.
                             |        -- Mark Twain