Error message output

[Polytropon]

On Mon, 21 Sep 2020 09:09:37 +0100, Steve O'Hara-Smith wrote:
> On Sun, 20 Sep 2020 22:12:24 -0700
> David Christensen <dpchrist at holgerdanske.com> wrote:
> 
> > I have been migrating my programming style towards a data flow paradigm, 
> > which includes "command-line filters".  So, an "ideal" command-line 
> > program or script would:
> > 
> > * Use stdin for the input data.
> > 
> > * Use stdout for the output data.
> > 
> > * Use configuration files, command-line options and arguments, received 
> > signals and direct tty reads for out-of-band/ non-data input.
> 
> 	This is where the standard set of unix devices is lacking, I have
> long thought that there should be a stdctl then stdin/stdout are data flow
> and stdtctl/stderr are control flow.

At least that is something known in "mainframe land": While
the file SYSPRINT is intended for program messages, i. e.,
things the program has to say about what it does, a different
file is used for program output, for example SYSUT2 (but it
doesn't have to be that one). But not everything is that clear:
SYSIN can be used to control the program, but PARM= can also
serve this purpose, while STDIN can instead contain input data
for the program to process.

And don't get me started about DCL... ;-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...