I've been seeing the subject line in a number of modules recently. Is
there any way:
1. require could be taught to recognize "unofficial" letter-patches?
2. PATCHLEVEL in Config.pm could be taught to recognize them?
3. (skating out onto thinner ice) release numbers could roll over
-- that is, use a number instead of an unofficial patch letter -- with
slightly greater frequency? (It seems like 5.001e and 5.001m have been de
facto releases, based on the number of messages I've seen that begin,
"First, upgrade to 5.001m. Then...".)
To be clear, I don't intend #3 to mean, "Work faster!" Instead, my
suggestion is that the version numbers accessible through require are not
keeping up with the speed of the work that is being done, and module
authors are "comment"-ing on that fact.
This came to mind as I found myself writing '#really requires 5.001m', and
wondering if there isn't some way to return a more meaningful error message
if 'm' isn't there. This is particularly a problem for modules, which the
user didn't write and maybe didn't even install. '$version = `perl -v`;'
doesn't seem like a great solution -- does another one exist?
M. Hedlund <hedlund@best.com>
there any way:
1. require could be taught to recognize "unofficial" letter-patches?
2. PATCHLEVEL in Config.pm could be taught to recognize them?
3. (skating out onto thinner ice) release numbers could roll over
-- that is, use a number instead of an unofficial patch letter -- with
slightly greater frequency? (It seems like 5.001e and 5.001m have been de
facto releases, based on the number of messages I've seen that begin,
"First, upgrade to 5.001m. Then...".)
To be clear, I don't intend #3 to mean, "Work faster!" Instead, my
suggestion is that the version numbers accessible through require are not
keeping up with the speed of the work that is being done, and module
authors are "comment"-ing on that fact.
This came to mind as I found myself writing '#really requires 5.001m', and
wondering if there isn't some way to return a more meaningful error message
if 'm' isn't there. This is particularly a problem for modules, which the
user didn't write and maybe didn't even install. '$version = `perl -v`;'
doesn't seem like a great solution -- does another one exist?
M. Hedlund <hedlund@best.com>