Re: Apocalypse 4 on perl.com

Wow! This is going to be torture waiting for all this to get done.

The given/when idea is very wonderful in a Perly kind of way.

I must confess that I've never been a big fan of try catch blocks (let alone nested ones); how they seem to move the core code further and further to the right. I always like that Perl could just take problems on the end. (... or die, ... || $foo = "bar"). Still, it's very nice to have that funcitonality in there.

I love reading Larry's respect for the humble origins of the language. Not force feeding a specific programming philosophy down peoples throats. Forcing stricter rules for modules and classes is a brilliant solution.

Comment on Re: Apocalypse 4 on perl.com

Replies are listed 'Best First'.
Re: Re: Apocalypse 4 on perl.com by Anonymous Monk on Jan 23, 2002 at 08:54 UTC
I think Larry Wall is brilliant at deconstructing classic CS ideas. I think the deconstruction of classes in perl5 was really revealing to me (I was a C++ fan at that time). Now he is deconstructing try-throw-catch. I personally love exception handling. I find `foo() or die()` tiresome, but the alternative of not checking every return value is unthinkable. You said "how they seem to move the core code further and further to the right". I interpret that to mean that the error handling (which I don't see as "core code") farther away form the code it is error checking or just a case of indent-itis. Both can be ameliorated by using more fine grained use of try-throw-catch. Using these blocks more often will limit nesting and keep error handling close to the code it handles.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Apocalypse 4 on perl.com
by Anonymous Monk on Jan 23, 2002 at 08:54 UTC

Now he is deconstructing try-throw-catch.

I personally love exception handling. I find foo() or die() tiresome, but the alternative of not checking every return value is unthinkable.

You said "how they seem to move the core code further and further to the right". I interpret that to mean that the error handling (which I don't see as "core code") farther away form the code it is error checking or just a case of indent-itis. Both can be ameliorated by using more fine grained use of try-throw-catch. Using these blocks more often will limit nesting and keep error handling close to the code it handles.

[reply]
[d/l]