**{x,y} quantifier

2007-07-01 Thread Amir E. Aharoni
(I'm just studying the intricacies of Perl 6, so please correct me if i say something stupid or if this has already been discussed before.) I was looking for the Perl 6 equivalent of "aaa" =~ /a{1,3}/ and finally found that it's "aaa" ~~ /a**{1 .. 3}/ This looked rather weird, so i asked on I

Re: **{x,y} quantifier

2007-07-01 Thread Luke Palmer
On 7/1/07, Amir E. Aharoni <[EMAIL PROTECTED]> wrote: I got the reply that it is similar to exponentiation of variables in math: a ** 5 == a * a * a * a * a == a It makes sense after it is explained and i do like the rationalization of the range as a list-like range, instead of the comma, b

Re: **{x,y} quantifier

2007-07-01 Thread Amir E. Aharoni
> please correct me if > i say something stupid or if this has already been discussed before.) Another important loss if we were to go with <1..3> would be the ability to have runtime-dependent ranges; e.g.: / ($ntimes) x**{$ntimes} / That's exactly what i meant by "something stupid". T

Re: **{x,y} quantifier

2007-07-01 Thread Luke Palmer
On 7/1/07, Amir E. Aharoni <[EMAIL PROTECTED]> wrote: > > please correct me if > > i say something stupid or if this has already been discussed before.) > Another important loss if we were to go with <1..3> would be the > ability to have runtime-dependent ranges; e.g.: > > / ($ntimes) x**{$n

Named captures (was: **{x,y} quantifier)

2007-07-01 Thread Amir E. Aharoni
On 01/07/07, Luke Palmer <[EMAIL PROTECTED]> wrote: On 7/1/07, Amir E. Aharoni <[EMAIL PROTECTED]> wrote: > > > please correct me if > > > i say something stupid or if this has already been discussed before.) > > > Another important loss if we were to go with <1..3> would be the > > ability to ha

Re: Named captures (was: **{x,y} quantifier)

2007-07-01 Thread Luke Palmer
On 7/1/07, Amir E. Aharoni <[EMAIL PROTECTED]> wrote: On 01/07/07, Luke Palmer <[EMAIL PROTECTED]> wrote: > / $ntimes := (\d+) x**{$ntimes} / The examples of := usage in S05 seem to have notation such as this: $ := (\d+) Yes, that is correct. I've been away from the Perl 6 community

[perl #43463] [BUG] Parrot Bug Summary "Requestors with most open tickets" doesn't DWIM

2007-07-01 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #43463] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43463 > --- osname= linux osvers= 2.6.15 arch= i386-linux-thread-multi cc= cc --- Flags:

About the headerizer

2007-07-01 Thread Andy Lester
http://www.perlfoundation.org/parrot/index.cgi?headerizer I've started this page as my brain dump of ideas until I get it into a proper .pod file. Please add to it, or ask questions on the page, as you see fit. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petd

Re: [svn:parrot] r19520 - in trunk: compilers/imcc config/gen/makefiles src

2007-07-01 Thread chromatic
On Sunday 01 July 2007 07:38:02 [EMAIL PROTECTED] wrote: > Author: petdance > Date: Sun Jul 1 07:38:01 2007 > New Revision: 19520 > > Modified: >trunk/compilers/imcc/imc.h >trunk/compilers/imcc/imcparser.c >trunk/compilers/imcc/main.c >trunk/compilers/imcc/parser_util.c >trunk

A problem about IPC::Open2

2007-07-01 Thread Liang He
Hello, I'm a beginner of the PERL language and I have troubles in understanding a PERL program these days. Actually I've been confused for a long time.I hope you can look into this program and point out the problem for me:) The program is in the attachment.It's a bit long , but the error occured

[perl #43453] [PATCH] typos in docs/configuration.pod

2007-07-01 Thread via RT
# New Ticket Created by Bob Wilkinson # Please include the string: [perl #43453] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43453 > Hello A couple of typos in docs/configuration.pod. [EMAIL PROTECTED]:~/src/parro

[perl #43462] [PATCH] some clearups, illegal memory accessing

2007-07-01 Thread via RT
# New Ticket Created by Bram Geron # Please include the string: [perl #43462] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43462 > Firstly, there are some clearups in , I think they're self-explanatory. Secondly, I disco

Re: A problem about IPC::Open2

2007-07-01 Thread Nir Pengas
unsubscribe

[perl #43452] [PATCH] typo in docs/compiler_faq.pod

2007-07-01 Thread via RT
# New Ticket Created by Bob Wilkinson # Please include the string: [perl #43452] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43452 > Hello A typo in docs/compiler_faq.pod. [EMAIL PROTECTED]:~/src/parrot/docs$ svn

[perl #43462] [PATCH] some clearups, illegal memory accessing

2007-07-01 Thread Bob Rogers
From: Bram Geron (via RT) <[EMAIL PROTECTED]> Date: Sun, 01 Jul 2007 03:53:50 -0700 # New Ticket Created by Bram Geron # Please include the string: [perl #43462] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?

Re: [svn:parrot] r19530 - in trunk/lib/Parrot: . Test

2007-07-01 Thread chromatic
On Sunday 01 July 2007 15:35:57 [EMAIL PROTECTED] wrote: > [lib] Removed conditional declaration problems so that code conforms to > perl coding standards I'm not convinced this is right. (I've long thought that this policy was broken with regard to local declarations, which completely fails to

[perl #43462] [PATCH] some clearups, illegal memory accessing

2007-07-01 Thread Bob Rogers
From: Bram Geron (via RT) <[EMAIL PROTECTED]> Date: Sun, 01 Jul 2007 03:53:50 -0700 # New Ticket Created by Bram Geron # Please include the string: [perl #43462] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?

Re: A problem about IPC::Open2

2007-07-01 Thread Jonathan Lang
Admittedly, that wasn't particularly germane to the perl6 mailing list; but it did bring up an issue that's been bothering me for a while. I would like to see Perl6 handle the equivalent of IPC::Open2 using the same sort of syntax and semantics that it uses for sockets, by default. That is, I'd

[perl #43453] [PATCH] typos in docs/configuration.pod

2007-07-01 Thread James Keenan via RT
Applied, along with some other small POD grammatical corrections, in r19532.

[perl #43452] [PATCH] typo in docs/compiler_faq.pod

2007-07-01 Thread James Keenan via RT
Applied with one small change in r19533.

Re: [svn:parrot] r19533 - trunk/docs

2007-07-01 Thread Andy Lester
On Jul 1, 2007, at 8:53 PM, [EMAIL PROTECTED] wrote: -You can either do so with an interger type id: +You can do so either with an integer type id: While we're going down the cleanup road, I'd really like to see ID spelled "ID", not "id". As a variable name, id is fine. In English text,