Re: Fortran write(print) problem
- From: Richard E Maine <nospam@xxxxxxxxxxxxx>
- Date: Sat, 27 Aug 2005 19:16:54 -0700
In article <43101BF9.6040506@xxxxxxxxxxxxxxxxxx>,
Brooks Moses <bmoses-nospam@xxxxxxxxxxxxxxxxxx> wrote:
> Yes. You've specified "*" formatting, which means (essentially) that
> you don't care about the details of how it looks so long as you can read
> it. Some compilers print out *-formatted lines with spaces in front of
> them; some don't.
Those that don't were violating the standard. To my knowledge, most or
all of them have been fixed (possibly with compiler switches to ask for
the nonstandard behavior).
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.
Brooks gave the recommended solution, which I won't repeat.
--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain | experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
.
- Follow-Ups:
- Re: Fortran write(print) problem
- From: Brooks Moses
- Re: Fortran write(print) problem
- References:
- Fortran write(print) problem
- From: Wang Jun
- Re: Fortran write(print) problem
- From: Brooks Moses
- Fortran write(print) problem
- Prev by Date: Re: maximum array size for g77 compiler
- Next by Date: Re: NLEQ1 and open source Fortran
- Previous by thread: Re: Fortran write(print) problem
- Next by thread: Re: Fortran write(print) problem
- Index(es):
Relevant Pages
|
|