Re: writing output listing onto screen (or not) and onto file
- From: Richard Maine <nospam@xxxxxxxxxxxxx>
- Date: Mon, 17 Jul 2006 19:30:50 -0700
On Mon, 17 Jul 2006 18:19:50 -0700, Terry wrote
(in article <1153185590.206914.127980@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>):
Just define an interger*4 variable IOUNIT
Default integer is better. There is no benefit to specifying the nonstandard
*4 here. That adds system dependence with no balancing benefit. Sometimes
there are good reasons for system dependence, but it is completely
superfluous here.
and set it to 0 for screen
output, or 2 (say) for printer or anything from 6 up (wiser) for a disk
device file..
Those numbers are compiler-dependent. In particular, the 0 is not
particularly universal. By far the most common number is that unit 6 is often
standard output.
Other aspects of the OP's question are addressed in other followups.
--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.
- References:
- writing output listing onto screen (or not) and onto file
- From: Bernard Bru
- Re: writing output listing onto screen (or not) and onto file
- From: Tim Prince
- Re: writing output listing onto screen (or not) and onto file
- From: bru
- Re: writing output listing onto screen (or not) and onto file
- From: jwm
- Re: writing output listing onto screen (or not) and onto file
- From: bru
- Re: writing output listing onto screen (or not) and onto file
- From: Terry
- writing output listing onto screen (or not) and onto file
- Prev by Date: Re: recl on g95 and gfortran
- Previous by thread: Re: writing output listing onto screen (or not) and onto file
- Next by thread: Re: writing output listing onto screen (or not) and onto file
- Index(es):