While goto may be harmful and all, I have a need to use it in this case and it makes logical sense for the program flow. I'm trying to avoid hackind it with a loop, but my goto statement isn't working. Here's a code sample:
ASK_DATABASE: ask('databasetype','Database type?','mysql'); my $found = undef; foreach $cur (@databases) { if (getConf('databasetype') eq $cur) { $found = 1; last; } } unless ($found) { output "Sorry, invalid option\n\n"; goto ASK_DATABASE; }
This runs fine as long as I enter a valid database type (as defined in @databases), but if I enter something invalid, instead of goto'ing back to the call to ask() again, I get this: Can't find label ASK_DATABASE at Conf/NewConfiguration.cm line 49, <STDIN> line 7. If anyone has a recomendation on how best to fix this, it would be great.

In reply to On goto by zachlipton

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &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.