Your suggestion works,
but only for explicitly parameterized parameters.
There may be parameters that I don't know of,
but nevertheless may affect my protected-caller.
Therefore I want ALL parameters protected.
Thanks, Jos

-----Original Message-----
From: racket-users@googlegroups.com [mailto:racket-users@googlegroups.com]
On Behalf Of jon stenerson
Sent: miƩrcoles, 13 de enero de 2016 0:50
To: racket-users@googlegroups.com
Subject: Re: [racket-users] Calling a procedure without allowing it to
permanently alter parameters.

Can you use this instead?

(define (protected-caller thunk)
   (parameterize ([p 'anything])
     (thunk)))

Works for me

Jon

-- 
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to