🚀 go-pugleaf

In article <1juom5INNgak@darkstar.UCSC.EDU>, spencer@cats.ucsc.edu
(Michael Spencer) writes:
|> 
|> 
|> esova@magnus.acs.ohio-state.edu (Edward R Sova) writes:
|> 
|> >Where can I get the Unix tee command for DOS?  You can split
redirection and
|> >piping.  like maybe foo | tee > prn >logfile.  Well I'm not sure of the 
|> >syntax, and I don't care right now, but I think you see what I want.  Where
|> >is it?  Thanx
|> 
|> Roll your own. Code goes something like this:
|> 
|> while (! feof(stdin))  {
|> 	fgets (str, 255, stdin);
|> 	fputs (str, stderr);		// send to screen
|> 	fputs (str, stdout);		// send whereever directed
|> 	}
|> fflush (stderr);
|> fflush (stdout);
|> close (dup(fileno(stdout)));		// ensure flushing on stdout

Note that these are not the "tee" semantics that we all know and love.
The command line is

	tee [ -i ] [ -a ] [ file ] ...

where -i is "ignore interrupts", which we don't care about, "-a" is to
append rather than overwrite existing files, and "file" and following
are the names of zero or more files into which a copy of stdin is
written, along with being sent to stdout.

So, technically, you'd want to open a vector of zero or more files, and
write each line into each of them as well as onto stdout.  This is a
few more lines of code, but still not exactly a nightmare.

- donl mathis at Silicon Graphics Computer Systems, Mountain View, CA
donl@sgi.com