Well, if I had to remove the goto, I would rewrite it as:

 
{
    eval {
        tie %session, 'Apache::Session::MySQL', $session, {
            Handle => HH::DB->db_Main, LockHandle => HH::DB->db_Main
        }
    };

    if ($@) {
        if ($@ =~ /^Object does not exist/) {
            $session = undef;
            redo;
        } else {
            print $cgi->header;
            die_nice('Database Error', 'Unable to connect at this time
+');
        }
    }
}
[download]

But a redo (just like next and last is just a glorified goto. People who just balk at any sight of a goto have at best heard about Dijkstra's article Go To Considered Harmful (which wasn't titles bij Dijkstra, but by Hoare), but never read the paper, or not understood it. Dijkstra just warns that goto can easily lead to unstructured programs, he doesn't say it's evil all the time.

Knuth has also written about this subject, in his Structured Programming with the Go To statement. His view is less far away from Dijkstra as that the titles suggest.

Abigail

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.