Nicely spotted, Thanks++.
I thought that I was misunderstanding the XS code when it appeared to be issuing the error unconditionally.
I never even looked at the "bugs" section. I think that's because I took the error "CV isn't complete", to mean that there was something wrong with the CV itself, rather than something wrong with the way Devel::Size was using or reporting it.
Maybe the message should read "Size for CV is incomplete", that would at least give some clue as to where and what the message meant.
Even better if it read "Devel::Size: Sizes for CVs are incomplete".
Indeed, I will change mine to read that way, and offer it as a patch to the owner. Along with something that I feel is sadly lacking from the documentation of many (almost all?). A simple section headed:
Messages: warning and error texts originating from this module.
It would make it a lot easier to find if such texts were in the POD (and generated HTML). I did a grep of my local Perl directory before posting the OP, but I didn't find it because I had the PPM version of the module, which doesn't contain the source. It does contain the HTML though.
Examine what is said, not who speaks.
"But you should never overestimate the ingenuity of the sceptics to come up with a counter-argument." -Myles Allen
"Think for yourself!" - Abigail
"Time is a poor substitute for thought"--theorbtwo
"Efficiency is intelligent laziness." -David Dunham
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
|