If I use an 'import' routine that looks for a version number (regardless of whether it has been stringified or not) it can compare them as version numbers.

As an example, download 'Xporter' from cpan and place it in the module, and then call the module -- you'll see that it flags an error.

You could argue that version strings should have some other use, but I'd much prefer something that looks like a version string be given preference to being interpreted as a version string.

I've yet to see any module accept a version-looking string as an argument. Not to say one couldn't exist, but it breaks the 'least astonishment' design principle, for the same expression to be taken as a version number in the module, but not in the useing module.

Obviously someone felt differently when designing the versions, but do you know of any modules that use a version looking string as an argument in a use module statement?

Looking at the link of anon-monk, I see the example using single quotes in the $VERSION statement, a recommendation against using v-strings and a use of a bare version number with 'use'.

I don't see why it is that way.