I do the same as you do. The convenience of doing parameter validation early on and bailing out early on is IMO that it binds parameter validation visually to the function (if that makes sense). When you're skimming over the function while reading the code, it's easy to see what parameters are expected and what their format and restrictions are.
Also, I find that it helps me focus when I write a function: first, validate parameters, then worry about the algorithm / implementation / whatever without having to think about invalid parms.
So, for the sake of self-documenting code, I'd put param validation at the top of the function. The added exit area is not so much of a problem, as you're still only exiting at the start or end, not in the guts of the routine.
CU
Robartes-
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.