Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Apocalypse 4 Online More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

A question (Score:2, Interesting)

by eann (93)

About 3/4 of the way down page 5 [perl.com], Larry answers the RFC's request for a subroutine to execute on_catch_enter or on_catch_exit with a suggestion to use temp "provided the implementation is smart enough to look for those hooks".

Maybe I didn't understand the original question--I do admit to not reading the RFC--or Larry's explanation of how stuff fits together. Since CATCH is a closure, why can't it just have its own PRE and POST blocks? Something like:

try { # ... CATCH {

--
$email =~ s/0/o/;
- Re:A question (Score:3, Informative)
  
  by TimToady (2729) on 2002.01.22 15:13 (#3523)
  
  PRE and POST would only fire off on that particular CATCH. The hooks in question would fire off on any CATCH within the dynamic scope.
  Larry
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.