[EMAIL PROTECTED] writes:
> +Placeholder names may only be lowercase, not because we're mean, but
> +because it helps us catch references to obsolete Perl 5 variables such as
> $^O.
That seems unnecessarily restrictive. How about "may not consist
solely of uppercase letters" instead? That would
Author: larry
Date: Sat Aug 4 09:06:15 2007
New Revision: 14434
Modified:
doc/trunk/design/syn/S06.pod
Log:
relaxed restriction on placeholders as suggested by Aaron Crane++
Modified: doc/trunk/design/syn/S06.pod
==
On Thu, Aug 02, 2007 at 04:19:18PM -0700, [EMAIL PROTECTED] wrote:
> Increment of a C (in a suitable container) works similarly to
> Perl 5, but is generalized slightly. First, the string is examined
> to see if it could be the string representation of a number in
> any common representation,
On Sat, Aug 04, 2007 at 12:55:58PM -0500, Patrick R. Michaud wrote:
: On Thu, Aug 02, 2007 at 04:19:18PM -0700, [EMAIL PROTECTED] wrote:
: > Increment of a C (in a suitable container) works similarly to
: > Perl 5, but is generalized slightly. First, the string is examined
: > to see if it coul
On Sat, Aug 04, 2007 at 12:56:06PM -0700, Larry Wall wrote:
: multi token numrange:<0x> (--> StrHex){ '0x' <[0..9a..fA..F]>+ }
Though sanity would probably force us to use numerics internally anyway
as the canonical comparison form, or we'd have trouble getting
'0x00' .. '0x0Ff'
to
On Sat, Aug 04, 2007 at 12:56:06PM -0700, Larry Wall wrote:
> for '❶' .. '❿' { .say }
>
> But it's not clear what to do if you try to increment ❿ though.
> Probably just return a failure.
Assuming that '❶' .. '❿' is a range similar to '0'..'9', then
consistency with the other ranges would see
