Searched refs:diagnostics (Results 1 - 12 of 12) sorted by relevance

/osnet-11/usr/src/cmd/perl/5.8.4/distrib/utils/
H A Dsplain.PL24 $IN = File::Spec->catfile(File::Spec->updir, 'lib', 'diagnostics.pm');
42 print OUT unless /^package diagnostics/;
H A DMakefile69 splain: ../lib/diagnostics.pm
/osnet-11/usr/src/cmd/perl/5.8.4/distrib/lib/
H A Ddiagnostics.pm1 package diagnostics; package
5 diagnostics, splain - produce verbose warning diagnostics
9 Using the C<diagnostics> pragma:
11 use diagnostics;
12 use diagnostics -verbose;
14 enable diagnostics;
15 disable diagnostics;
24 =head2 The C<diagnostics> Pragma
26 This module extends the terse diagnostics normall
[all...]
H A DTest.pm237 ok($have, $expect, $diagnostics);
390 # diagnostics.
597 Although test failures should be enough, extra diagnostics can be
608 be used to generate extremely sophisticated diagnostics for a
H A DAutoSplit.pm130 C<AutoSplit> will also emit general diagnostics for inability to
/osnet-11/usr/src/cmd/perl/5.8.4/distrib/pod/
H A Dpodselect.PL48 use diagnostics;
H A Dpod2usage.PL48 use diagnostics;
H A Dpod2text.PL218 produce the following diagnostics:
/osnet-11/usr/src/cmd/perl/5.8.4/distrib/lib/Test/
H A DMore.pm119 utilities. Various ways to say "ok" with better diagnostics,
258 Should an ok() fail, it will produce some diagnostics:
296 So why use these? They produce better diagnostics on failure. ok()
368 diagnostics on failure.
509 The diagnostics of this test normally just refer to 'the object'. If
H A DBuilder.pm830 Normally, Test::Builder does some extra diagnostics when the test
972 Where diagnostics about todo test failures and diag() should go.
/osnet-11/usr/src/cmd/perl/5.8.4/distrib/lib/Text/
H A DBalanced.pm2155 Accessing C<$@-E<gt>{error}> returns one of the error diagnostics listed
2162 The available diagnostics are:
/osnet-11/usr/src/cmd/perl/5.8.4/distrib/lib/Pod/
H A DParser.pm190 non-zero value will cause B<Pod::Parser> to issue diagnostics for
204 #use diagnostics;

Completed in 51 milliseconds