There has been several discussions in the past about convincing management that CPAN modules are trustworthy, reliable, etc. Alas, unlike link master tilly, I can't rapidly give you a pointer to these nodes.
As your title so aptly uses, FUD is difficult to overcome, especially engineer to management (vs engineer to engineer). Ovid had a major problem with his boss trying to write everything in house, and introducing a really trashed CGI argument processor.
Possibly, your best argument may be that anything that you (that being either you personally, your team, your department, or your company) can write is going to be far worse than any conceivable perceived holes in CGI.pm.
If you can't use CGI.pm, how is he proposing that you achieve the goal?
--Chris
e-mail jcwren
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.