1. Make a *complete* check on perldiag.pod and propose a patch.
   My first scan shows me that perldiag.pod is hopelessly out of sync

   example:

   lt09:/pro/3gl/CPAN 126 > grep -r "t resolve method" perl/
   perl/pod/perltoc.pod:use, Cannot resolve method `%s' overloading `%s' in package `%s', Constant
   perl/pod/perldiag.pod:=item Can't resolve method `%s' overloading `%s' in package `%s'
   perl/pod/perl5004delta.pod:=item Cannot resolve method `%s' overloading `%s' in package `%s'
   lt09:/pro/3gl/CPAN 127 >

   Where is that message issued?

   The check is to be made both ways.
   - What messages are issued and not in diag
   - What messages are in diag but never issued
   - What messages are in diag and issued, but not in sync