I'm guessing that you are writing this code and then uploading it to a remote site for rendering. This might explain your testing it from the cgi-bin rather than from a command line. This is less than ideal, because being able to test compile success is much easier when you get a direct response.

Even when you test code through a web server, Perl very nicely reports what it doesn't like, and you can find these reports in your web server error log. For most typographic errors, this will give enough information to correct code compile failures.

Once you are comfortable with the web development process, you can then use 'warn' alerts to determine execution process results and errors.

Of course, being able to test your code locally first is best.

---

---

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! —

• 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, 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:
	&		&
	<		&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.