Re: Fortran write(print) problem

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. I find myself curious as to how this came about whenever I run across it.

- Brooks


--
The "bmoses-nospam" address is valid; no unmunging needed.
.

Relevant Pages

  • Re: Is C99 the final C? (some suggestions)
    ... > that someone will try compile their stuff on an old compiler. ... > because the ANSI standard obsoleted them, and everyone picked up the ANSI ... fixed by using another language. ... >>are multiplying two expressions of the widest type supported by your ...
    (comp.lang.c)
  • Re: Statement on Schildt submitted to wikipedia today
    ... to working programmers and more with being "right all the time, ... so that compiler developers could be shed ... The major corporate interests were compiler developers, ... processors, committed to standard division semantics, and otherwise ...
    (comp.lang.c.moderated)
  • Re: Is tab[x++] = val undefined?
    ... increment the value of x ... As it is the only write to x that is to do to x it does not matter ... Which of the steps is done first is left to the compiler as freedom to ... The standard describes that rules unabigous. ...
    (comp.std.c)
  • Re: #define and (brackets)
    ... Minor compiler vendors are free to join if they are so inclined, ... analysis hasn't changed between the two versions of the standard. ... This bug is a minor bug in an obscure ...
    (microsoft.public.vc.language)
  • Re: interesting use of NEXT SENTENCE vs. CONTINUE
    ... Program name in quotes (allowed in '02 Standard) ... > If J can be made an independent item which the compiler can put wherever it ... > has to be associated with a hardware device in SPECIAL-NAMES. ... > that ALTER *always* modifies the address parameter of the hardware branch ...
    (comp.lang.cobol)