Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!sri-unix!DBrown@HI-MULTICS.ARPA
From: DBrown@HI-MULTICS.ARPA
Newsgroups: net.unix
Subject: Re: Lest we forget: MULTICS
Message-ID: <1963@sri-arpa.UUCP>
Date: Fri, 13-Jul-84 11:16:00 EDT
Article-I.D.: sri-arpa.1963
Posted: Fri Jul 13 11:16:00 1984
Date-Received: Thu, 19-Jul-84 02:26:22 EDT
Lines: 11

Re pipes & linking:
  dynamic linking ad pipes have little relation to each other.
  the Multics equivalent of a pipe ia an active function, which returns
its result as a string for the command interpreter to use (much like the
x = `some_program` construct in the Unix shell).
  pipes avoid having data written to a (possibly huge) tempfile before
further processing can continue, and are therefore reall more of an
interprocess communication than a linking mechanism.
  Dynamic linking, in retrospect, is mostly usefull in maintenance of
existing progras, not development.  (about which, much later)
 --dave (unix hack on a 'bun) brown