Test thread safety

[perl/modules/re-engine-Plugin.git] / Plugin.pod

diff --git a/Plugin.pod b/Plugin.pod
index c71d1ef3a47e76d959579e692a0af43502827cf3..5910f14e2e49bdd727475717a93dee28a6b3e011 100644 (file)
--- a/Plugin.pod
+++ b/Plugin.pod
@@ -265,6 +265,19 @@ done it'll allow the binding of C<%+> and C<%-> and support the
 L<Tie::Hash> methods FETCH, STORE, DELETE, CLEAR, EXISTS, FIRSTKEY,
 NEXTKEY and SCALAR.
 
+=head1 CONSTANTS
+
+=head2 C<REP_THREADSAFE>
+
+True iff the module could have been built with thread-safety features
+enabled.
+
+=head2 C<REP_FORKSAFE>
+
+True iff this module could have been built with fork-safety features
+enabled. This will always be true except on Windows where it's false
+for perl 5.10.0 and below.
+
 =head1 Tainting
 
 The only way to untaint an existing variable in Perl is to use it as a
@@ -419,6 +432,15 @@ tests.
 
 =back
 
+=head1 DEPENDENCIES
+
+L<perl> 5.10.
+
+A C compiler.
+This module may happen to build with a C++ compiler as well, but don't rely on it, as no guarantee is made in this regard.
+
+L<XSLoader> (standard since perl 5.006).
+
 =head1 BUGS
 
 Please report any bugs that aren't already listed at
@@ -435,7 +457,7 @@ Vincent Pit C<< <perl at profvince.com> >>
 
 Copyright 2007,2008 E<AElig>var ArnfjE<ouml>rE<eth> Bjarmason.
 
-Copyright 2009,2010 Vincent Pit.
+Copyright 2009,2010,2011 Vincent Pit.
 
 This program is free software; you can redistribute it and/or modify it
 under the same terms as Perl itself.