Re: advance=no problem

glen herrmannsfeldt <gah@[EMAIL PROTECTED]
> writes:

>> rudra <bnrj.rudra@[EMAIL PROTECTED]
> wrote:

>>> dear friends,
>>> i am using ifort compiler in linux.
>>> when i am trying to write something like
>>> write(*,'(1x,'a20',advance='no')"STARTING CALCULATION"

> (snip)

>>> i am expecting the program to write "STARTING CALCULATION" at the
>>> beginning of the calc; 

> (snip)

>> You need to flush the output buffer after the first write.  The system
>> is just trying to be more efficient by buffering its output.  It has
>> no idea in advance how long the computation is going to take.

> The C/unix tradition is that terminal output (either stderr, or
> stdout not redirected to a file) is unbuffered.  The output will
> appear immediately without the need for fflush().  When going
> to a file or even a pipe it is buffered and normally doesn't appear
> immediately.
>
> I believe there is some historical connection between
> ADVANCE="NO" and C stream output.  I am pretty sure the
> Fortran standard doesn't require unbuffered (in the unix
> sense) output, but it might be considered
> a "quality of implementation" issue.
>
> If you are writing to a file, expect it to be buffered.

The OP did say that his program is "writing the whole line in one go",
which sure sounds like the first WRITE statement's output was buffered,
for whatever reason.