From: Casey West <casey@geeknest.com>
Date: Sun, 6 Jul 2003 18:24:46 +0000 (-0400)
Subject: Re: [perl #5025] #line directive explination wrong
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=7b6e93a8eae54981596267b3f4e1a1710fdea071;p=p5sagit%2Fp5-mst-13.2.git

Re: [perl #5025] #line directive explination wrong
Message-ID: <20030706222446.GL7506@geeknest.com>

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

diff --git a/pod/perlsyn.pod b/pod/perlsyn.pod
index d5fe7fb..608c0cd 100644
--- a/pod/perlsyn.pod
+++ b/pod/perlsyn.pod
@@ -638,11 +638,11 @@ C preprocessors: it matches the regular expression
     # example: '# line 42 "new_filename.plx"'
     /^#    \s*
       line \s+ (\d+)   \s*
-      (?:\s"([^"]+)")? \s*
+      (?:\s("?)([^"]+)\2)? \s*
      $/x
 
-with C<$1> being the line number for the next line, and C<$2> being
-the optional filename (specified within quotes).
+with C<$1> being the line number for the next line, and C<$3> being
+the optional filename (specified with or without quotes).
 
 There is a fairly obvious gotcha included with the line directive:
 Debuggers and profilers will only show the last source line to appear