Wow, I didn't know it was going to be quite this
I like Tye's idea of possibly using a separate sub-module (Net::Ping::Dangerous? ;) that might incorporate some of the more elaborate approaches, and then letting Net::Ping know about it. I can see that some of my earlier trouble in using Net::Ping came from possibly not understanding the security implications of making system calls from a Perl module, even though this might be an effective approach.
Perhaps some of the biggest improvements could come from not just looking at the code, but also by adding a Troublesooting section to the Net::Ping documentation? If it was more specific that the module might behave unexpectedly because of 1. These 2. Possible 3. Conditions, there would probably not be as much confusion and questions from people using it.
In any case, this is a great thread, Falkkin, and you write some convincing arguments, as do AgentM and Tye. Great weekend reading. ;-)
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||