Path: utzoo!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!aunro!aupair.cs.athabascau.ca!atha!decwrl!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!eniac.seas.upenn.edu!jeffe
From: jeffe@eniac.seas.upenn.edu (George Jefferson )
Newsgroups: comp.lang.postscript
Subject: defeating save/restore (summary)
Message-ID: <39120@netnews.upenn.edu>
Date: 14 Mar 91 02:01:45 GMT
References: <38972@netnews.upenn.edu> <1909@chinacat.Unicom.COM> <1991Mar11.145130.12027@cl.cam.ac.uk>
Sender: news@netnews.upenn.edu
Reply-To: jeffe@eniac.seas.upenn.edu (George Jefferson )
Organization: University of Pennsylvania
Lines: 34
Nntp-Posting-Host: eniac.seas.upenn.edu


I basically got two responses.

Many people sugested leaving my value on the stack.
 I suppose my question was not as well posed as it could have been,
 but there is a _lot_ of code between the 'restore' and the place where
 I am allowed to insert my code.  I would have to be very careful with 
 the stack indeed :-)

Several people mentioned the feature/bug of strings being exempt from
 restore - ing.  I am trying to write something which will be very
 portable, but I think I would try this as a last resort.

my own answer was..
 think of a way to avoid the problem..

thanks to all these people
(and probably a few that I missed)

John Kohl
Leland Woodbury
Robert A. Lerche
Dick Dunn
Berthold K.P. Horn
Jacques Kors
Mark Zellers
Frank Jensen
Luigi Perrotta
Chris Thompson
woody


--
-george            george@mech.seas.upenn.edu