In addition to what other monks have said:

• Don't use mixed case style in variable and subroutine names. It is ugly and unreadable IMHO. Use all lowercase, and separate words with _ (underscore). However, if you're maintaining code, you may choose to stick with the existing convention. (s/doSomething/do_something/ - much better...)

• Use short, familiar names for short lived variables and long, descriptive names for long lived ones. Don't try to "compress" or "pack" many words or concepts into a cryptic, unspellable variable name. A few more keystrokes will save you many a headache two weeks later. Anyway, what does the "l" in $lResponce stand for?

  Besides, I think it should be the other way around: $response in the inner sub block, and $lxxxxx_response in the outer scope. (substitute lxxxxx with the answer to my previous question)

---

---

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.