Re: Formatted IO of huge/tiny values
- From: Clive Page <junk@xxxxxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 09:46:36 +0000
In message <1hcardp.1w7jbpsaeuq6sN%nospam@xxxxxxxxxxxxx>, Richard E Maine <nospam@xxxxxxxxxxxxx> writes
I tend to think exactly the opposite - that list-directed is for
quick&dirty work. People shouldn't use it if they care about fine
details. And I tend to personally prefer that list-directed err in the
direction of legibility by not having overly high precision.
For what it's worth, I agree with Richard that list-directed should not be encouraged for serious use. But I can see that there may be situations where you really want to read a number previously written number without altering its value and where unformatted I/O won't work.
I'd like to suggest that maybe in a future standard that the Gw.d format should be defined to do this, given suitable values of w and d? G is rarely used (in my experience, anyway) and essentially means that you specify the field width and number of decimal places but leave the details to the Fortran run-time system.
--
Clive Page
.
- Follow-Ups:
- Re: Formatted IO of huge/tiny values
- From: Joost
- Re: Formatted IO of huge/tiny values
- References:
- Formatted IO of huge/tiny values
- From: Janne Blomqvist
- Re: Formatted IO of huge/tiny values
- From: Richard E Maine
- Re: Formatted IO of huge/tiny values
- From: James Giles
- Re: Formatted IO of huge/tiny values
- From: Richard E Maine
- Formatted IO of huge/tiny values
- Prev by Date: Re: a system_clock that doesn't roll
- Next by Date: Re: generalized WHILE() extension/feature?
- Previous by thread: Re: Formatted IO of huge/tiny values
- Next by thread: Re: Formatted IO of huge/tiny values
- Index(es):
Relevant Pages
|
