Re: Fortran write(print) problem



Brooks Moses <bmoses-nospam@xxxxxxxxxxxxxxxxxx> wrote:
>Richard E Maine wrote:
>> Although I agree (and have regularly said) that the general rule is that
>> * formatting is for when you don't care about the details, this
>> particular case is not even a matter where the compiler might or might
>> not do what you want. In this case, the standard actually *REQUIRES*
>> the compiler to do what you don't want (even if some compilers have been
>> known to violate the standard). The reasons for that are historical.

>If you don't mind the telling, I'd like to hear the historical reasons.

The first character in a printed line was interpreted as a (hardware)
carriage control character. ' ' meant a new line, '1' a new page,
'+' overprinting, and possibly a few others that I've forgotten.

The 'asa' utility on Unix systems is usually used to convert this to
something more Unixish.
.



Relevant Pages

  • Re: Bloated file size?
    ... > about it a lot because the compiler does it for them so they don't have ... Fortran formatting has an awful lot of options. ... formatting support in Fortran is providing a lot of capability that ...
    (comp.lang.fortran)
  • Re: [PATCH] mask ADT: new mask.h file [2/22]
    ... don't care invariant ... These invariants can be changed transparently. ... semantics while not incurring the overhead of indirection for smaller ... Compiler-specific operational semantics and compiler version ...
    (Linux-Kernel)
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    ... The compiler can also reorder non-volatile accesses. ... (which you definitely _do_ care about). ... The compiler is prohibited from moving a volatile access across a sequence ...
    (Linux-Kernel)
  • Re: Text wrapping in output under Intel compiler
    ... use when you don't care about the details of the output formatting. ... a "compiler option" to control this; it is called an explicit format ... With list-directed formatting, the details of the output format are not ...
    (comp.lang.fortran)
  • Re: Aspiring highest-order programmer
    ... There's no reason a compiler can't emit object code. ... > Probably not, but i do think that one, as driver, become more 'at one' ... > with your car when you've at least done some mechanical work yourself. ... Otherwise you may not care for your car ...
    (comp.programming)