[PATCH] Rephrase a part of perlcall.pod more clearly.

---
 pod/perlcall.pod |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 359e097..54b2145 100644
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -323,13 +323,13 @@ See I<Using G_EVAL> for details on using G_EVAL.
 
 You may have noticed that using the G_EVAL flag described above will
 B<always> clear the C<$@> variable and set it to a string describing
-the error iff there was an error in the called code.  This unqualified
-resetting of C<$@> can be problematic in the reliable identification of
-errors using the C<eval {}> mechanism, because the possibility exists
-that perl will call other code (end of block processing code, for
-example) between the time the error causes C<$@> to be set within
-C<eval {}>, and the subsequent statement which checks for the value of
-C<$@> gets executed in the user's script.
+the error if and only if there was an error in the called code.  This
+unqualified resetting of C<$@> can be problematic in the reliable
+identification of errors using the C<eval {}> mechanism, because the
+possibility exists that perl will call other code (end of block
+processing code, for example) between the time the error causes C<$@>
+to be set within C<eval {}>, and the subsequent statement which checks
+for the value of C<$@> gets executed in the user's script.
 
 This scenario will mostly be applicable to code that is meant to be
 called from within destructors, asynchronous callbacks, signal
-- 
1.7.1

• [PATCH] Fix typo in perlcall. by Florian Ragwitz
• Re: [PATCH] Fix typo in perlcall. by Ben Morrow
• Re: [PATCH] Fix typo in perlcall. by Florian Ragwitz
• [PATCH] Rephrase a part of perlcall.pod more clearly. by Florian Ragwitz