develooper Front page | perl.perl5.porters | Postings from March 2013

Re: [perl #116683] Diagnostics not listed in perldiag.pod

Thread Previous | Thread Next
From:
Tony Cook
Date:
March 3, 2013 00:36
Subject:
Re: [perl #116683] Diagnostics not listed in perldiag.pod
Message ID:
20130303003603.GB13455@mars.tony.develop-help.com
On Thu, Feb 28, 2013 at 06:54:13PM -0800, James E Keenan via RT wrote:
> On Thu Feb 07 20:10:39 2013, demerphq wrote:
> > This is a bug report for perl from demerphq@gmail.com,
> > generated with the help of perlbug 1.39 running under perl 5.12.4.
> > 
> > 
> > -----------------------------------------------------------------
> > [Please describe your issue here]
> > 
> > Perl diag is missing many entries, which are in turn TODO tests
> > in t/porting/diag.t
> > 
> > This is a task that could be handled by someone without C skills.
> > 
> > Note this bug is about *blead* perl, the below status is from my
> > system perl.
> > 
> 
> I glanced at this ticket tonight and soon saw one problem in tackling it.
> 
> When I run t/porting/diag.t, I get this output in the section for file gv.c:
> 
> ##########
> not ok 127 - Can't locate object method "%s" via package "%s" (perhaps
> you forgot to load "%s"?) # TODO in DATA
...
> 
> This suggests that a certain portion of the diagnostics marked as TODO
> in t/porting/diag.t have, in fact, been done.  How should we proceed?

Perhaps add another section in DATA for diagnostics known to be
covered, but not detected as covered.  Entries would preferably
include a comment about how they're covered.

Your example is a good case where it would be difficult or confusing
to update the documentation to include both the base and the extended
message.

Tony

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About