I was hoping a more experienced person can direct me what I am doing wrong on this NT script??
A: No strictures, no warnings, no parameter validation.
A subroutine should always check its parameters. If you use Carp::Assert you can turn it off for production and on for development. If you had basic parameter validation then it would be clear to you that no parameters were being passed to the subroutine.
The merits of strict and warnings are discussed in so many nodes on this site it isnt funny. Peruse them, especially Use strict warnings and diagnostics or die
Also grinders comments are spot on.
Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look.
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.