Path: utzoo!yunexus!davecb
From: davecb@yunexus.UUCP (David Collier-Brown)
Newsgroups: comp.sw.components
Subject: Re: a comment on Using components (shorter)
Summary: history repeateth...
Message-ID: <1911@yunexus.UUCP>
Date: 13 May 89 01:56:29 GMT
Article-I.D.: yunexus.1911
References: <11293@bloom-beacon.MIT.EDU> <3579@eos.UUCP> <1080@ginosko.samsung.com> <3594@eos.UUCP> <14479@duke.cs.duke.edu>
Reply-To: davecb@yunexus.UUCP (David Collier-Brown)
Organization: Bimodal: [Interleaf Canada | York U. Computing Services]
Lines: 31

| In article <3594@eos.UUCP> eugene@eos.UUCP (Eugene Miya) writes:
| ... the really neat thing I thought
| about Unix software tools was they kept much of the library function
| while also being executable programs.  There was the spline program
| and the spine function.

In article <14479@duke.cs.duke.edu> gm@romeo.UUCP (Greg McGary) writes:
| Yes, this is a `really neat thing' but not something I usually think
| of as a feature of UNIX.  If anything, this isn't done anywhere nearly
| often enough.

   Hmmn.  
   If memory serves, that was a carry-over from Multics.  The mutlicks
 standards manual strongly suggested you write a set of functions which
 fit a standardized external interface, and directed you to something
 called the subsystems utility package, which would ease the writing
 of such an interface.

   To return to the present, a standard interface package for either
 a line-of-text style or an icon-and-menu style might make a component 
 which would make writing framework for other components easier....


 --dave (7 more days until monomania!) c-b
--
David Collier-Brown,  | {toronto area...}lethe!dave
72 Abitibi Ave.,      |  Joyce C-B:
Willowdale, Ontario,  |     He's so smart he's dumb.
CANADA. 223-8968      |