comment on

I wrote this to discuss another thing: what you think about right attitude, goal and priorities used while developing reusable software like CPAN modules. Do you agree reliability and security must be 1st and 2nd priorities, or not and why?

If that is truly what your asking, you sure went out of your way to hide it...

Reliability and security must be 1st and 2nd priority to all CPAN authors? Of coarse not, generalizing any statement like that is folly. Blindly deciding to make reliability and security a priority without taking into account the purpose of a module is going to result in poorer programming in the long run. Each module's priority should be based on its purpose.

For example, why should the author of Acme-Apace-Werewolf make reliability and security a priority of his module? Technically, it doesn't even need to compile to serve its purpose.

In reply to Re: Reliable software OR Is CPAN the sacred cow by Unanimous Monk
in thread Reliable software: SOLVED (was: Reliable software OR Is CPAN the sacred cow) by powerman

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks