Re^4: Error(?): "CV isn't complete"?

Had it been anyone other than you I might have settled for just an email.

As it was, and given your workload, I wanted at least offer a patch properly. Get the latest sources; test on an up-to-date copy of Perl etc. Which meant downloading bleed-perl and I tend to leave big downloads to the weekend. One of the constraints of a narrow pipe.

Quite how you find the time to be bored amazes me, given your prolific involvement in so many things.

Update: Done.

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

Comment on Re^4: Error(?): "CV isn't complete"?

Replies are listed 'Best First'.
Re^5: Error(?): "CV isn't complete"? by Elian (Parson) on Nov 27, 2004 at 21:48 UTC
I got the patch and applied it, so the errors are a bit more distinguishable. I also, while I was at it, added in proper (mostly) sizing for filehandles and globs. (Globs were silently wrong -- sizing a glob should have counted everything in the glob, but it didn't, so the totals were a bit low. Now it does, and they aren't)	[reply]
Re^5: Error(?): "CV isn't complete"? by Elian (Parson) on Nov 22, 2004 at 15:08 UTC
The problem with being involved with so many things is that sometimes they're all stuck waiting on other things, or in the middle of some build or other that's long enough to trigger the "bored now" reflex, but not long enough to actually do anything meaningful. At those times I browse the web. :) I got the patch for this. Next time I'm waiting on a 15 minute compile I'll look at it, apply it, and cut a new release. Might fix up some of the other semi-implemented bits while I'm at it. (CVs aren't the only thing that Devel::Size can't get a good handle on)	[reply]