[libtest-warn-perl] 05/08: Refresh language.patch.
gregor herrmann
gregoa at debian.org
Sun Apr 6 16:17:53 UTC 2014
This is an automated email from the git hooks/post-receive script.
gregoa pushed a commit to branch master
in repository libtest-warn-perl.
commit 2c46694c10616c664ec58845d1f6d30ad9b01b62
Author: gregor herrmann <gregoa at debian.org>
Date: Sun Apr 6 18:14:05 2014 +0200
Refresh language.patch.
---
debian/patches/language.patch | 241 ++++++++++++++++++++----------------------
1 file changed, 114 insertions(+), 127 deletions(-)
diff --git a/debian/patches/language.patch b/debian/patches/language.patch
index 99c62eb..ed98d63 100644
--- a/debian/patches/language.patch
+++ b/debian/patches/language.patch
@@ -1,138 +1,125 @@
-Author: Jay Bonci <jaybonci at debian.org>
Description: Patch from Era Eriksson to clean up some manpage language
Bug-Debian: #322351
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=49519
-Reviewed-by: Nicholas Bamber <nicholas at periapt.co.uk>
+Author: Jay Bonci <jaybonci at debian.org>
Reviewed-by: gregor herrmann <gregoa at debian.org>
-Last-Update: 2013-06-08
+Last-Update: 2014-04-06
--- a/Warn.pm
+++ b/Warn.pm
@@ -31,9 +31,9 @@
-
- A good style of Perl programming calls for a lot of diverse regression tests.
-
--This module provides a few convenience methods for testing warning based code.
-+This module provides a few convenience methods for testing warning based-code.
-
--If you are not already familiar with the Test::More manpage
-+If you are not already familiar with the L<Test::More> manpage,
- now would be the time to go take a look.
-
- =head2 FUNCTIONS
+
+ A good style of Perl programming calls for a lot of diverse regression tests.
+
+-This module provides a few convenience methods for testing warning based code.
++This module provides a few convenience methods for testing warning based-code.
+
+-If you are not already familiar with the Test::More manpage
++If you are not already familiar with the L<Test::More> manpage,
+ now would be the time to go take a look.
+
+ =head2 FUNCTIONS
@@ -49,7 +49,7 @@
- Another way to say that there are no warnings in the block
- is C<warnings_are {foo()} [], "no warnings">.
-
--If you want to test for a warning given by Carp,
-+If you want to test for a warning given by Carp
- you have to write something like:
- C<warning_is {carp "msg"} {carped =E<gt> 'msg'}, "Test for a carped warning">.
- The test will fail if a "normal" warning is found instead of a "carped" one.
+ Another way to say that there are no warnings in the block
+ is C<warnings_are {foo()} [], "no warnings">.
+
+-If you want to test for a warning given by Carp,
++If you want to test for a warning given by Carp
+ you have to write something like:
+ C<warning_is {carp "msg"} {carped =E<gt> 'msg'}, "Test for a carped warning">.
+ The test will fail if a "normal" warning is found instead of a "carped" one.
@@ -95,10 +95,10 @@
- which in general has the form "WARNING at __FILE__ line __LINE__".
- So you can check for a warning in the file Foo.pm on line 5 with
- C<warning_like {bar()} qr/at Foo.pm line 5/, "Testname">.
--I don't know whether it's sensful to do such a test :-(
--However, you should be prepared as a matching with 'at', 'file', '\d'
-+Perhaps it is not sensible to perform such a test;
-+however, you should be aware that matching on a sweeping regular expression
- or similar will always pass.
--Think to the qr/^foo/ if you want to test for warning "foo something" in file foo.pl.
-+Consider qr/^foo/ if you want to test for warning "foo something" in file foo.pl.
-
- You can also write the regexp in a string as "/.../"
- instead of using the qr/.../ syntax.
+ which in general has the form "WARNING at __FILE__ line __LINE__".
+ So you can check for a warning in the file Foo.pm on line 5 with
+ C<warning_like {bar()} qr/at Foo.pm line 5/, "Testname">.
+-I don't know whether it makes sense to do such a test :-(
+-However, you should be prepared as a matching with 'at', 'file', '\d'
++Perhaps it is not sensible to perform such a test;
++however, you should be aware that matching on a sweeping regular expression
+ or similar will always pass.
+-Think to the qr/^foo/ if you want to test for warning "foo something" in file foo.pl.
++Consider qr/^foo/ if you want to test for warning "foo something" in file foo.pl.
+
+ You can also write the regexp in a string as "/.../"
+ instead of using the qr/.../ syntax.
@@ -106,7 +106,7 @@
- as strings without slashes are reserved for warning categories
- (to match warning categories as can be seen in the perllexwarn man page).
-
--Similar to C<warning_is>,
-+As with C<warning_is>,
- you can test for warnings via C<carp> with:
- C<warning_like {bar()} {carped => qr/bar called too early/i};>
-
-@@ -122,17 +122,17 @@
- Tests whether a BLOCK gives exactly one warning of the passed category.
- The categories are grouped in a tree,
- like it is expressed in perllexwarn.
--Note, that they have the hierarchical structure from perl 5.8.0,
--wich has a little bit changed to 5.6.1 or earlier versions
--(You can access the internal used tree with C<$Test::Warn::Categorization::tree>,
--although I wouldn't recommend it)
-+Note that they have the hierarchical structure from perl 5.8.0,
-+you can access the internal hierarchy with
-+C<$Test::Warn::Categorization::tree>,
-+although it isn't recommended).
-
- Thanks to the grouping in a tree,
--it's simple possible to test for an 'io' warning,
--instead for testing for a 'closed|exec|layer|newline|pipe|unopened' warning.
-+it's possible to test simply for an 'io' warning,
-+instead of testing for a 'closed|exec|layer|newline|pipe|unopened' warning.
-
--Note, that warnings occuring at compile time,
--can only be catched in an eval block. So
-+Note that compile-time warnings
-+can only be caught in an eval block. So
-
- warning_like {eval q/"$x"; $x;/}
- [qw/void uninitialized/],
-@@ -141,9 +141,8 @@
- will work,
- while it wouldn't work without the eval.
-
--Note, that it isn't possible yet,
--to test for own categories,
--created with warnings::register.
-+Note also that it isn't yet possible
-+to test for categories you created yourself with C<warnings::register>.
-
- =item warnings_like BLOCK ARRAYREF, TEST_NAME
-
-@@ -163,7 +162,7 @@
- {carped => qr/bar warning/i},
- 'io'
- ],
-- "I hope, you'll never have to write a test for so many warnings :-)";
-+ "I hope you'll never have to write a test for so many warnings :-)";
-
- =item warnings_exist BLOCK STRING|ARRAYREF, TEST_NAME
-
-@@ -188,19 +187,19 @@
-
- =head1 BUGS
-
--Please note that warnings with newlines inside are making a lot of trouble.
--The only sensible way to handle them is to use are the C<warning_like> or
--C<warnings_like> methods. Background for these problems is that there is no
--really secure way to distinguish between warnings with newlines and a tracing
-+Please note that warnings with newlines inside are very awkward.
-+The only sensible way to handle them is to use the C<warning_like> or
-+C<warnings_like> methods. The background is that there is no
-+really safe way to distinguish between warnings with newlines and a
- stacktrace.
-
--If a method has it's own warn handler,
-+If a method has its own warn handler,
- overwriting C<$SIG{__WARN__}>,
- my test warning methods won't get these warnings.
-
--The C<warning_like BLOCK CATEGORY, TEST_NAME> method isn't extremely tested.
--Please use this calling style with higher attention and
--tell me if you find a bug.
-+The C<warning_like BLOCK CATEGORY, TEST_NAME> method isn't fully tested.
-+Please take note if you use this this calling style,
-+and report any bugs you find.
-
- =head1 TODO
-
-@@ -213,7 +212,7 @@
-
- =head1 SEE ALSO
-
--Have a look to the similar modules: L<Test::Exception>, L<Test::Trap>.
-+Have a look to the similar L<Test::Exception> module. L<Test::Trap>
-
- =head1 THANKS
-
+ as strings without slashes are reserved for warning categories
+ (to match warning categories as can be seen in the perllexwarn man page).
+
+-Similar to C<warning_is>,
++As with C<warning_is>,
+ you can test for warnings via C<carp> with:
+ C<warning_like {bar()} {carped => qr/bar called too early/i};>
+
+@@ -126,10 +126,10 @@
+
+
+ Thanks to the grouping in a tree,
+-it's simple possible to test for an 'io' warning,
+-instead for testing for a 'closed|exec|layer|newline|pipe|unopened' warning.
++it's possible to test simply for an 'io' warning,
++instead of testing for a 'closed|exec|layer|newline|pipe|unopened' warning.
+
+-Note, that warnings occurring at compile time,
++Note that compile-time warnings
+ can only be caught in an eval block. So
+
+ warning_like {eval q/"$x"; $x;/}
+@@ -139,9 +139,8 @@
+ will work,
+ while it wouldn't work without the eval.
+
+-Note, that it isn't possible yet,
+-to test for own categories,
+-created with warnings::register.
++Note also that it isn't yet possible
++to test for categories you created yourself with C<warnings::register>.
+
+ =item warnings_like BLOCK ARRAYREF, TEST_NAME
+
+@@ -161,7 +160,7 @@
+ {carped => qr/bar warning/i},
+ 'io'
+ ],
+- "I hope, you'll never have to write a test for so many warnings :-)";
++ "I hope you'll never have to write a test for so many warnings :-)";
+
+ =item warnings_exist BLOCK STRING|ARRAYREF, TEST_NAME
+
+@@ -193,19 +192,19 @@
+ should be done to %warnings_in_category. You should look into perl source to check
+ how warning is looking exactly.
+
+-Please note that warnings with newlines inside are making a lot of trouble.
+-The only sensible way to handle them is to use are the C<warning_like> or
+-C<warnings_like> methods. Background for these problems is that there is no
+-really secure way to distinguish between warnings with newlines and a tracing
++Please note that warnings with newlines inside are very awkward.
++The only sensible way to handle them is to use the C<warning_like> or
++C<warnings_like> methods. The background is that there is no
++really safe way to distinguish between warnings with newlines and a
+ stacktrace.
+
+-If a method has it's own warn handler,
++If a method has its own warn handler,
+ overwriting C<$SIG{__WARN__}>,
+ my test warning methods won't get these warnings.
+
+-The C<warning_like BLOCK CATEGORY, TEST_NAME> method isn't extremely tested.
+-Please use this calling style with higher attention and
+-tell me if you find a bug.
++The C<warning_like BLOCK CATEGORY, TEST_NAME> method isn't fully tested.
++Please take note if you use this this calling style,
++and report any bugs you find.
+
+ =head1 TODO
+
+@@ -218,7 +217,7 @@
+
+ =head1 SEE ALSO
+
+-Have a look to the similar modules: L<Test::Exception>, L<Test::Trap>.
++Have a look to the similar L<Test::Exception> module. L<Test::Trap>
+
+ =head1 THANKS
+
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libtest-warn-perl.git
More information about the Pkg-perl-cvs-commits
mailing list