🚀 go-pugleaf

Actually, I think you want to put the old transfer function at
the *end* of the new transfer procedure to get the right
effect, since there's no guarantee that the two procedures are
commutative:
 
/newstuff { .... } def
% remember to disable packing so put can write into executable array
false setpacking        % real code should save current packing state
{ newstuff 0 exec } dup 1 currenttransfer put settransfer
 
The resulting transfer proc is
 
{ newstuff <oldtransfer> exec }
 
Is currenttransfer a variable or an operator?  If an operator, then the
following doesn't work:
 
{ currenttransfer } bind
 
If it's a variable, then you can just do this:
 
{ //currenttransfer exec }
 
Ken (shiva@well.sf.ca.us)