The processor choice in question is for additional newlines during the
data transfer; the initial one is not at the processor's option.
It's not a question of the _initial_ new line,
but of a new line being implied (or not) by a new row
when the array is specified as a whole array.
I can see where (9.5.2) [192:20-22] the whole array
is a sequence of scalar list items in array element order.
I don't see any mention of rank, nor new rows etc.
Most :-) of 9.5.3 speaks to Derived Type I/O. Anyway,
I missed any mention of new rows starting new lines.
List-directed is the wrong approach for the OP because of the additional
newlines that might be added at the processor's option.
Re: WRITE + new line ... >> The processor choice in question is for additional newlines during the ... >> data transfer; the initial one is not at the processor's option. ... > when the array is specified as a whole array. ... That is not a whole array form and, ... (comp.lang.fortran)
disk speed issues ... I am continuing to build by sunfire box with a cx300 san array.... unfortunately everything is fine except for very different data transfer... when I move a file from internal disk to the array it ... (SunManagers)
Re: Save an array to memory for another program to read it ...Dan Nagle wrote: ... I need the program to store into memory this array, end itself and when immediately runs again to load this array again from the memory. ... (comp.lang.fortran)
