New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnostics not listed in perldiag.pod #12761
Comments
From @demerphqCreated by @demerphqPerl diag is missing many entries, which are in turn TODO tests 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. Perl Info
|
From @demerphqnot ok 1 - The telldir() function is not implemented on NetWare # TODO in DATA |
From @jkeenanOn Thu Feb 07 20:10:39 2013, demerphq wrote:
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: ########## In point of fact, this warning *is* covered in pod/perldiag.pod -- but ########## This suggests that a certain portion of the diagnostics marked as TODO Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @tonycozOn Thu, Feb 28, 2013 at 06:54:13PM -0800, James E Keenan via RT wrote:
Perhaps add another section in DATA for diagnostics known to be Your example is a good case where it would be difficult or confusing Tony |
From @nwc10On Sun, Mar 03, 2013 at 11:36:03AM +1100, Tony Cook wrote:
I think that the test already has a system for dealing with things like this. Whilst adding comments to C code technically is editing C, I don't think Nicholas Clark |
Migrated from rt.perl.org#116683 (status was 'open')
Searchable as RT116683$
The text was updated successfully, but these errors were encountered: