Sometimes that extra semicolon can really mess you up...

You must have had another EOT somewhere in the file, because it should have given you one of these: Can't find string terminator "EOT" anywhere before EOF at ... So between the first terminating EOT and the second terminating EOT you had the @forminputs variable and perl thought you wanted to print the variable name along with all the other code in between.

That's why it's helpful to give your here-document labels different names each time, like:

print <<EOT1; EOT1 print << EOT2; EOT2
That way if you accidentally put a semicolon on the end of one you'll immediately know where to look because you'll get the error above instead of some other crazy errors.

In reply to RE: RE: Re: @forminputs annoying error by httptech
in thread @forminputs annoying error by damian

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.