a proper patch for C<< >>:
--- ext/threads/shared/shared.pm.old 2003-02-10 15:08:03.000000000 +1100
+++ ext/threads/shared/shared.pm 2003-02-11 10:24:51.000000000 +1100
@@ -182,10 +182,10 @@
autovivify the elements, and neither does slicing a shared array/hash
over non-existent indices/keys autovivify the elements.
-share() allows you to C<share $hashref->{key}> without giving any error
-message. But the C<$hashref->{key}> is B<not> shared, causing the error
+share() allows you to C<< share $hashref->{key} >> without giving any error
+message. But the C<< $hashref->{key} >> is B<not> shared, causing the error
"locking can only be used on shared values" to occur when you attempt to
-C<lock $hasref->{key}>.
+C<< lock $hashref->{key} >>.
=head1 AUTHOR
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
