comment on

Programmers count from 0. :-)

All versions of my (only) CPAN module had no known bugs when I released them (and the test code to show that the known bugs where fixed). That didn't really mean they had no bugs.

You point about API changes is valid, but that an API is "complete" doesn't mean it's "done". It takes a LOT of testing and tweaking to get an API "just right" - so I myself prefer to keep the right to make "minor" changes to an API for quite some time.

The 1.0 version number is arbitrary and for marketing purposes only. The associated software is never bug-free, never finished, and ususally deprecated within a couple of weeks. Programmers should know better than to trust a version number.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re^2: Review: CGI::Prototype by Joost
in thread Review: CGI::Prototype by dragonchild

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: the Markov chain saw
	PerlMonks