Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Sep 2020 09:09:37 +0100
From:      Steve O'Hara-Smith <steve@sohara.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Error message output
Message-ID:  <20200921090937.fc1fbed5bdcd9615d77ea8f4@sohara.org>
In-Reply-To: <528b2c90-18c4-9e95-a150-67344154c66c@holgerdanske.com>
References:  <20200920191108.22864e5c.freebsd@edvax.de> <528b2c90-18c4-9e95-a150-67344154c66c@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sun, 20 Sep 2020 22:12:24 -0700
David Christensen <dpchrist@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.

> * Use stderr, log files, and the exit value for out-of-band/ non-data 
> output.

-- 
Steve O'Hara-Smith <steve@sohara.org>



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200921090937.fc1fbed5bdcd9615d77ea8f4>