Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!julius.cs.uiuc.edu!psuvax1!swatsun!jeremy
From: jeremy@cs.swarthmore.edu (Jeremy Brest)
Newsgroups: comp.sys.mac.misc
Subject: Re: System 7.0 vs. NeXT Step
Message-ID: <NK5W6CQ@cs.swarthmore.edu>
Date: 24 Jan 91 00:08:41 GMT
References: <11468@helios.TAMU.EDU> <1991Jan23.204448.23778@unx2.ucc.okstate.edu>
Distribution: comp
Organization: Swarthmore College, PA, USA
Lines: 29

In <1991Jan23.204448.23778@unx2.ucc.okstate.edu> minich@unx2.ucc.okstate.edu (Robert Minich) writes:

>by n138ct@tamuts.tamu.edu (Brent Burton):

>| Pipes?

>No. Pipes don't make a lot of sense without stdin and stdout, do
>they? :-) 

I guess I don't follow you.  This is a quote of the pipe(2) man page: 

(NAME
(    pipe - create an interprocess communication channel
(
(SYNOPSIS
(     pipe(fildes)
(     int fildes[2];
(
(DESCRIPTION
(     The pipe system call creates an I/O mechanism called a pipe.
(     The file descriptors returned can be used in read and write
(     operations.  When the pipe is written using the descriptor
(     fildes[1] up to 4096 bytes of data are buffered before the
(     writing process is suspended.  A read using the descriptor
(     fildes[0] will pick up the data.

What does this have to do with stdin and stdout?

Jeremy Brest