Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!snorkelwacker!bloom-beacon!WILKINS.BCM.TMC.EDU!dinah
From: dinah@WILKINS.BCM.TMC.EDU (Dinah Anderson)
Newsgroups: comp.windows.x
Subject: Re: imake documentation woes
Message-ID: <9007251354.AA04770@NICOLLE.IAIMS.BCM.TMC.EDU>
Date: 25 Jul 90 13:54:48 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 22



To add to Marc's list of what he'd like to see in a document on imake:

1) Clear, concise documentation of all the cases imake can handle 
  (from include files to man pages) and how to build your own macro if
   your specific case has not been addressed.

2) Maybe a list of some commonly asked questions (with answers of course.)

3) I think a case study with step by step instructions would be valuable.
   We just changed over to using Imake on a big project here and once I 
   figured out how to restructure the source and whipped up some sample 
   Imakefiles, it only took me and 2 other people a few hours to get to the
   point where a make World would work. The programmers were impressed at 
   how painless it was. (Of course I spared them the agony of figuring out
   how Imake actually works.)


Dinah Anderson					 Manager of Systems Integration
Baylor College of Medicine	                                 Houston, Texas
internet: dinah@bcm.tmc.edu                   uucp: {rutgers,mailrus}!bcm!dinah