Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pt.cs.cmu.edu!egc From: egc@CS.CMU.EDU (eddie caplan) Newsgroups: comp.windows.x Subject: Re: imake documentation woes Message-ID: Date: 25 Jul 90 16:02:07 GMT References: <595@servio.UUCP> <2816@uakari.primate.wisc.edu> Organization: School of Computer Science, Carnegie Mellon University Lines: 30 In-reply-to: bin@primate.wisc.edu's message of 25 Jul 90 05:10:28 GMT In article <2816@uakari.primate.wisc.edu> bin@primate.wisc.edu writes: > >From article <595@servio.UUCP>, by marcs@servio.UUCP (Marc San Soucie): > >What is the problem that Imake purports to solve > >I'm not sure that to fill the gaps in imake documentation that it's >as important to *justify* imake as to *explain* it. i agree with Marc. good documentation of any sort needs to clearly, in laymens' terms as much as possible, establish the context and justification of the accompanying technical material. thanks, and say what you mean. -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% INTERNET: caplan@cs.cmu.edu BITNET: caplan%cs.cmu.edu@cmuccvma CSNET: caplan%cs.cmu.edu@relay.cs.net UUCP: ...!seismo!cs.cmu.edu!caplan USPS: eddie caplan, c/o school of comp sci, cmu, pittsburgh, pa 15213-3890 phone: (412) 268-6426 a good engineer is a good thief. bennet, thanks for the signature. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% INTERNET: caplan@cs.cmu.edu BITNET: caplan%cs.cmu.edu@cmuccvma