Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!julius.cs.uiuc.edu!apple!well!shiva
From: shiva@well.sf.ca.us (Kenneth Porter)
Newsgroups: comp.lang.postscript
Subject: Re: A question about //add
Summary: // and systemdict operators
Message-ID: <21745@well.sf.ca.us>
Date: 21 Nov 90 15:46:48 GMT
References: <1990Nov12.195235.13908@light.uucp> <321@heaven.woodside.ca.us> <1990Nov14.170020.16233@light.uucp>
Lines: 19



orthlieb@adobe.UUCP (Carl Orthlieb) writes:
 
> It is suggested that // not be used, use bind or load
> depending on the effect you want.
 
// is particularly useful for re-defining system operators in
heavily nested situations:
 
/showpage { stuff //showpage more-stuff } def
 
The problem here is that one has to test for whether the system operator
has be re-defined before;  if so, then an exec has to be added after
the name:
 
/systemname load operatortype { /systemname { //systemname } def } if
 
Ken (shiva@well.sf.ca.us)