[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue EXIT-EXTENT
- To: sandra%defun@cs.utah.edu (Sandra J Loosemore)
- Subject: Re: issue EXIT-EXTENT
- From: masinter.pa@Xerox.COM
- Date: 31 Oct 88 14:47 PST
- Cc: masinter.pa@Xerox.COM, sandra%defun@cs.ARPA (Sandra J Loosemore), cl-cleanup@sail.stanford.edu
- In-reply-to: sandra%defun@cs.utah.edu (Sandra J Loosemore)'s message of Mon, 31 Oct 88 14:58:26 MST
The proposal would separate the extent of the visibility of the CATCH tag
from the actual extent of the exit. The CATCH tag would still be visible to
the THROW inside the UNWIND-PROTECT cleanup clause, it would merely be an
"error" to execute that THROW. This is similar to the situation with BLOCK
tags, where
(FUNCALL (BLOCK FOO #'(LAMBDA () (RETURN-FROM FOO 3))))
is an error because, while the scope FOO in the RETURN-FROM allows the FOO
returned from to name the one in the BLOCK, the extent has ended.