Path: utzoo!attcan!utgpu!watmath!att!dptg!rutgers!apple!sun-barr!cs.utexas.edu!uunet!mcsun!ukc!icdoc!qmc-cs!harlqn!jcgs
From: jcgs@wundt.harlqn.uucp (John Sturdy)
Newsgroups: comp.lang.postscript
Subject: Re: Building A PostScript Toolset
Message-ID: <JCGS.89Aug30235308@wundt.harlqn.uucp>
Date: 30 Aug 89 22:53:08 GMT
References: <2251@optilink.UUCP>
Sender: news@harlqn.UUCP
Organization: Harlequin Ltd, Cambridge, England
Lines: 22
In-reply-to: cramer@optilink.UUCP's message of 29 Aug 89 22:29:13 GMT

Yes, that's a fine idea. But let's be organized about procedure
naming! It would be good to make these toolbits into ProcSets (as in
EPSF %%BeginProcSet etc) and it would be even better to be able to
concatenate them to build prologues, without worrying about name
clashes.

My suggestion here (clumsy but effective) is to give each chunk a
string name, and use that string at the start of each name that the
chunk describes globally. Taking that a little further, they could be
given some EPSF description other than ProcSet, thus telling handlers
that, unlike ProcSets, they can be concatenated safely to make
prologues.

--
__John            When asked to attend a court case, Father Moses took with him
          a leaking jug of water. Asked about it, he said: "You ask me to judge
               the faults of another, while mine run out like water behind me."

                jcgs@uk.co.harlqn (UK notation) jcgs@harlqn.co.uk (most places)
    ...!mcvax!ukc!harlqn!jcgs (uucp - really has more stages, but ukc knows us)
John Sturdy                                            Telephone +44-223-872522
                      Harlequin Ltd, Barrington Hall, Barrington, Cambridge, UK