comment on

Ditto!!!

I am usually a little wary of COMPILED modules these days, ones that I can't see the implemtation of. But CPAN is and hopefully will always be open source. It seems then that most arguments against CPAN modules that start out with "I do not trust code I didn't write" really become "I don't understand how the module works, so I'll ignore it and write it myself."

And to this DAY, people still insist on keeping this attitude. I guess this is to be expected - maybe MicroSoft has made everyone paranoid about using someone else's code, I mean, do we really know that there aren't any backdoors in MicroSoft's COM objects.

Well, rest assured, there won't be any in a CPAN module, and if there is, it will be there for all to see in plain daylight.

Jeff

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

In reply to (jeffa) Re: A Fit on NIH by jeffa
in thread A Fit on NIH by footpad

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks