[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl6-language
Subject:    r28899 - docs/Perl6/Spec
From:       pugs-commits () feather ! perl6 ! nl
Date:       2009-10-26 16:19:31
Message-ID: 20091026161931.22678.qmail () feather ! perl6 ! nl
[Download RAW message or body]

Author: lwall
Date: 2009-10-26 17:19:30 +0100 (Mon, 26 Oct 2009)
New Revision: 28899

Modified:
   docs/Perl6/Spec/S05-regex.pod
Log:
[S05] spec that /$var/ warns and fails if $var is undefined


Modified: docs/Perl6/Spec/S05-regex.pod
===================================================================
--- docs/Perl6/Spec/S05-regex.pod	2009-10-26 15:16:09 UTC (rev 28898)
+++ docs/Perl6/Spec/S05-regex.pod	2009-10-26 16:19:30 UTC (rev 28899)
@@ -16,8 +16,8 @@
 
     Created: 24 Jun 2002
 
-    Last Modified: 13 Sep 2009
-    Version: 103
+    Last Modified: 26 Oct 2009
+    Version: 104
 
 This document summarizes Apocalypse 5, which is about the new regex
 syntax.  We now try to call them I<regex> rather than "regular
@@ -979,6 +979,14 @@
 C<< <$var> >>.  (See assertions below.)  This form does not capture,
 and it fails if C<$var> is tainted.
 
+If C<$var> is undefined, a warning is issued and the match fails.
+
+[Conjecture: when we allow matching against non-string types, doing a
+type match on the current node will require the syntax of an embedded
+signature, not just a bare variable, so there is no need to account for
+a variable containing a type object, which is by definition undefined,
+and hence fails to match by the above rule.]
+
 However, a variable used as the left side of an alias or submatch
 operator is not used for matching.
 

[prev in list] [next in list] [prev in thread] [next in thread]