in reply to Re: CGI Error Handling
in thread CGI Error Handling

I like eval blocks 
eval {
    #any code in here
    yourSub();
}
if ($@){
    # $@ contains err message if error occurs
    warn " continue with script but there has been an erro $@ \n";
    #run error handling routine
    ErrorHandle();
}

[download]

The average user finds a standard Apache error page v scary so I try and make an error doc for every error possible. 

 
ErrorDocument 404 /missing.html
ErrorDocument 401 /auth_error.html

[download]

Update amended to consider below

Replies are listed 'Best First'.
Re (tilly) 3: CGI Error Handling
by tilly (Archbishop) on Dec 10, 2001 at 18:19 UTC
    Two important pieces of advice.

    The first is to pick an indentation style indenting between 2-4 spaces, and then start using it. Now. Running your code through perltidy will show you what it looks like.

    The second is to call functions with explicit parameters. That means using parens. As documented in perlsub, if you use just the plain & and in a function you call another function, that other function will get the parameters to the first as arguments.

    Believe me. You may think these are picky details. But they are not. The first strongly impacts how easy it is to pick out your logic at a glance. The second is causing a subtle set of side-effects that may or may not be intended which a maintainance programmer may or may not know enough to notice.

[reply]
      thanks pure lazyness on my part inbred by auto indenting text editors and tab keys.
[reply]

In Section Seekers of Perl Wisdom