Perl-Sensitive Sunglasses | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Agreed. I have done many projects where version numbering is integer-only. So a Version "1" means it's the first ever version of that module, and probably quite buggy. I used Integers, so i wouldn't have to deal with floating-point bugs in a number of automated deployment and validation scripts. In my opinion, version numbers only have to do two things: 1) Make sense to the Author. 2) Increase with every version so that PAUSE/CPAN/BackPAN stuff sees them as "newer" One of the projects i mentioned above is a web/worker framework. When dynamically loading modules (for a specific project), it checks the version number of that module and only accepts it if it's the same version as the framework. So, occasionally, i have to bump some projects version number without any other changes (so looking *only* at that project, some people may be confused). Reason behind this is simple: A new framework version usually has some API changes, so i want to make sure all projects based on that get a once-over when upgrading the framework and i'm not unwittingly running into upgrade woes.
perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
In reply to Re^9: Perl Contempt in My Workplace
by cavac
|
|