Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool2.mu.edu!think.com!paperboy!hsdndev!cmcl2!phri!roy From: roy@phri.nyu.edu (Roy Smith) Newsgroups: comp.sys.mac.misc Subject: Re: 7.0 CAN pipe (was Re: System 7.0 vs. NeXT Step) Message-ID: <1991Jan28.203027.13702@phri.nyu.edu> Date: 28 Jan 91 20:30:27 GMT References: <11468@helios.TAMU.EDU> <1991Jan23.204448.23778@unx2.ucc.okstate.edu> <5646@idunno.Princeton.EDU> <2898@casbah.acns.nwu.edu> <1991Jan25.092823.16868@cpsc.ucalgary.ca> Sender: news@phri.nyu.edu (News System) Organization: Public Health Research Institute, New York City Lines: 19 francis@uchicago.edu (Francis Stracke) writes: > It sounds like what Mess-Dos calls a pipe, sure. But you don't get any > communication until the app is finished. Under Unix, data is sent to a > special buffer, and the receiving app can read it any time. Historical note: there was once a version of Unix that was designed to run on, I believe, LSI-11's with limited memory (which, at the time, probably meant less than 64k). To make it fit, the kernel was stripped of everything that could possibly be taken out, including the pipe code. The shell still supported pipes, however; you could do "foo | bar" which the shell just turned into "foo > temp; bar < temp" for you. No, I never used this version, I just remember reading about it in an old issue of BSTJ. My guess is that it never made it out of The Labs. -- Roy Smith, Public Health Research Institute 455 First Avenue, New York, NY 10016 roy@alanine.phri.nyu.edu -OR- {att,cmcl2,rutgers,hombre}!phri!roy "Arcane? Did you say arcane? It wouldn't be Unix if it wasn't arcane!"