update FT2 Changes

[imager.git] / lib / Imager / Threads.pod

diff --git a/lib/Imager/Threads.pod b/lib/Imager/Threads.pod
index a99a995a03099c6fd3d605ddcaf321ac91b0a464..86c96feb549de078f52d0d4ebffd5990f6ac1291 100644 (file)
--- a/lib/Imager/Threads.pod
+++ b/lib/Imager/Threads.pod
@@ -12,7 +12,7 @@ Imager::Threads - Imager and threads
 
 =head1 DESCRIPTION
 
-Starting from version 0.93 Imager attempts to work safely with perl's
+Starting from version 0.94 Imager attempts to work safely with perl's
 C<ithreads>.
 
 Previous versions stored some state in global variables, in particular
@@ -52,18 +52,19 @@ attempt to read or write TIFF or GIF files, or work with Type 1 fonts.
 
 =item *
 
-Fill, font, color or I/O layer objects created in one thread and are
+Fill, font, color or I/O layer objects created in one thread are not
 valid for use in child threads.  If you manage to duplicate such an
 object in another thread, you get to keep both pieces when it breaks.
 
 =back
 
-Note that if you have another module using C<libtiff> or C<giflib> it
-may interact with Imager's use of those libraries in a threaded
-environment, since there's no way to co-ordinate access to the global
-information C<libtiff> and C<giflib> maintain.
+Note that if you have another module using C<libtiff>, C<giflib> or
+C<t1lib> it may interact with Imager's use of those libraries in a
+threaded environment, since there's no way to co-ordinate access to
+the global information C<libtiff>, C<giflib> and C<t1lib> maintain.
 
-Imager currently doesn't use threads itself.
+Imager currently doesn't use threads itself, except for testing its
+threads support.
 
 =head1 SEE ALSO