So if return; is just as right as return(); , but twice as fast, when would you use return(); ?

In general I wouldn't ;-)

I guess the only two reasons I can think of to prefer return () would be:

• For those people unfamiliar with Perl. In other languages a bare return has often has different semantics (e.g. value of last expression). Making it explicit may help people unfamiliar with Perl. However it would be much better to educate these users rather than code for them IMHO.
• If you were coding a routine that was only being called in list context then it might make sense to use return () just to make it a little more obvious that you were thinking in terms of lists rather than scalars in the code.

---

---

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.