🚀 go-pugleaf

In <6761@umd5.umd.edu> zben@umd5.umd.edu (Ben Cranston) writes:
>I could see initally writing an application to keep track of which parts
>of the prolog were actually used, but if you let the prolog procedures
>call each other it could be a maintenance nightmare keeping the
>caller/callee matrix updated.

No nightmare.  I wrote a Perl script to do this a few months ago.  We keep 
several hundred logos online that have been created by Adobe Illustrator or 
Adobe Streamline, and several hundred prologues add up to a lot of disk space. 
I went through the standard prologue by hand once and built up a dependency 
tree.  The Perl script uses an associative array to keep track of which tokens 
have been defined, and spits out necessary definitions as needed.  Yes, it 
messes up the prologue/script dichotomy for the sake of easy programming, 
but not doing so is left as an exercise to the reader.

John
-- 
john j. chew, iii   		  phone: +1 416 425 3818     AppleLink: CDA0329
trigraph, inc., toronto, canada   {uunet!utai!utcsri,utgpu,utzoo}!trigraph!john
dept. of math., u. of toronto     poslfit@{utorgpu.bitnet,gpu.utcs.utoronto.ca}