Re: writing output listing onto screen (or not) and onto file
- From: Ken Fairfield <my.full.name@xxxxxxxxx>
- Date: Mon, 17 Jul 2006 13:57:45 -0700
On 7/17/2006 8:15 AM, bru wrote:
[...snip example of selecting output units...]
Your solution seems to me to heavy because I have hundred of writes in my code!!
In priniciple, you could generalize jwm's example to any number of
units/files, but isolate the multiple WRITE's to a subroutine you've
written, e.g., MY_WRITE, and then replace all the WRITE's with
MY_WRITE's in your code. Unfortunately in practice, that may be
quite difficult because of needing to pass a variable number of
arguments to MY_WRITE. Only if the number of different combinations
of format, argument number and argument types is fairly small would
this be feasible (presumably be using a generic feature to overload
the finite number of different versions...).
-Ken
--
I don't speak for Intel, Intel doesn't speak for me...
Ken Fairfield
D1C Automation VMS System Support
who: kenneth dot h dot fairfield
where: intel dot com
.
- Follow-Ups:
- Re: writing output listing onto screen (or not) and onto file
- From: e p chandler
- Re: writing output listing onto screen (or not) and onto file
- 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
- writing output listing onto screen (or not) and onto file
- Prev by Date: Re: double confusion
- Next by Date: Re: I/O reading formated files
- 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):
Relevant Pages
|