From: Jarkko Hietaniemi <jhi@iki.fi>
Date: Mon, 4 Nov 2002 15:50:07 +0000 (+0000)
Subject: How pre-5.9.0 Perl can be fooled by a defined-or.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=5d9c98cd422c28eda066f2ffa94077448887483b;p=p5sagit%2Fp5-mst-13.2.git

How pre-5.9.0 Perl can be fooled by a defined-or.

p4raw-id: //depot/perl@18091
---

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index e1c9a06..4f9112b 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -3239,6 +3239,11 @@ or setgid bit set.  This doesn't make much sense.
 construct.  Remember that bracketing delimiters count nesting level.
 Missing the leading C<$> from a variable C<$m> may cause this error.
 
+Note that since Perlf 5.9.0 a // can also be the I<defined-or>
+construct, not just the empty search pattern.  Therefore code written
+in Perl 5.9.0 or later that uses the // as the I<defined-or> can be
+misparsed by pre-5.9.0 Perls as a non-terminated search pattern.
+
 =item %sseek() on unopened filehandle
 
 (W unopened) You tried to use the seek() or sysseek() function on a