Re: "Try? There is no try." -- Yoda's Exception handling syntax

[email protected] (Jonathan Scott Duff) Wed, 16 Aug 2000 00:33:50 -0500
Newsgroups perl.perl6.language.flow,perl.perl6.language.errors
Message-ID <[email protected]>
On Tue, Aug 15, 2000 at 04:12:17PM -0700, Peter Scott wrote:
> >Would someone please enlighten me as to the purpose of an explicit "try."
> 
> Well, for one, it makes it easier to see that a block is subject to 
> exception handling if all you have to do is look at the beginning for 'try' 
> rather than scan through it for a 'catch'.

On Tue, Aug 15, 2000 at 06:24:08PM -0600, Tony Olekshy wrote:
> The "try" is not necessarily for Perl's sake.  It's for the
> programmer's sake.  It says, watch out, some sort of non-local
> flow control may be going on here.  It signals intent to deal
> with action at a distance (unwinding semantics).

How important are the exceptions?  What about putting them first?

	exceptions { 
	   # code that does exception handling
	} 
	{
	   # code that may throw exceptions
	}

Note that's a two-block keyword.

> I don't think we should obfuscate classic try/throw/catch/finally
> from the ground up.  

I'm inclined to agree with you, but as you can see, I'm not letting
that hamper my brainstorming effort :-)

-Scott
-- 
Jonathan Scott Duff
[email protected]