On Sep 6, 2007, at 7:52 PM, James Keenan via RT wrote:
On Fri Jun 08 06:48:12 2007, ptc wrote:
In the file config/inter/make.pm, there is the following todo item:
# FIXME this is an ugly hack
# replace the value for $(MAKE) with the actual path or we'll
end up
# with
http://perlbuzz.com/project-hum/2007/09/first-mod-perl6-handlers.html
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Author: larry
Date: Thu Sep 6 20:56:39 2007
New Revision: 14453
Modified:
doc/trunk/design/syn/S03.pod
Log:
fixed it right this time...
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod
On Thu, Sep 06, 2007 at 08:32:55PM -0400, Joe Gottman wrote:
: Do the results of andthen and orelse really bind to ANY arguments of
: the second block? If the second block has two parameters it makes more
: sense to me for the results to bind to the first parameter and nothing
: to bind to th
Author: larry
Date: Thu Sep 6 20:50:04 2007
New Revision: 14452
Modified:
doc/trunk/design/syn/S03.pod
Log:
extra \ found by sunnavy++
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod
Author: larry
Date: Thu Sep 6 20:36:26 2007
New Revision: 14451
Modified:
doc/trunk/design/syn/S03.pod
Log:
typo spotted by sunnavy++
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod
Please review the patch attached, which consists of 5 new test files:
t/configure/109-inter_lex.01.t
... thru ...
t/configure/109-inter_lex.05.t
... as well as a refactored config/inter/lex.pm. The refactorings had
as their objectives (a) eliminating untestable parts of conditions; and
(b) provi
Author: larry
Date: Thu Sep 6 19:29:21 2007
New Revision: 14450
Modified:
doc/trunk/design/syn/S05.pod
Log:
typo from [particle]++
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/design/syn/S05.pod(o
Here is a new file for the purpose of testing config::inter::make. Due
to the fact that anyone who is running Parrot tests is highly likely to
have some version of 'make' on his/her box and is almost as likely to
have a version of 'gmake' there, it will be very hard to achieve
coverage of very bra
On 9/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> @@ -1254,6 +1273,17 @@
>
> =item *
>
> +A leading C indicates a positive zero-width assertion, and like C
> +merely reparses the rest of the assertion recursively as if the C
> +were not there. In addition to forcing zero-width, it also su
On Fri Jun 08 06:48:12 2007, ptc wrote:
> In the file config/inter/make.pm, there is the following todo item:
>
> # FIXME this is an ugly hack
> # replace the value for $(MAKE) with the actual path or we'll
end up
> # with a variable that recursively refers to itself
>
> T
Re-opening this ticket (hopefully briefly) to submit one more test file
to squeeze a bit more coverage out of the tests of config::init::hints.
Unless someone objects, I'll probably apply this tomorrow when I apply
patches for config::inter::progs.
Thank you very much.
kid51
105-init_hints.04
[EMAIL PROTECTED] wrote:
Author: larry
Date: Thu Sep 6 09:31:16 2007
New Revision: 14447
+
+C<< infix: >>, proceed on success
+
+test1() andthen test2()
+
+Returns the left argument if the left argument indicates failure
+(that is, if the result is undefined). Otherwise it
+evaluates and r
Author: larry
Date: Thu Sep 6 17:12:02 2007
New Revision: 14449
Modified:
doc/trunk/design/syn/S05.pod
Log:
old is now <+foo> to suppress capture
new now is zero-width like
clarifications on backtracking and longest-token semantics
minimal quantifiers are now considered to terminate a long
Larry Wall wrote:
> Jonathan Lang wrote:
> : So 'orelse' is exactly like '//', except that the result of the left
> : side gets passed to the right side as an error message. Is there a
> : reason to make this exception, as opposed to altering '//' to behave
> : exactly like 'orelse' does?
>
> How
On Thu, Sep 06, 2007 at 03:49:42PM -0700, Larry Wall wrote:
: On Thu, Sep 06, 2007 at 04:02:19PM -0500, Patrick R. Michaud wrote:
: : I agree. One thought I had was that perhaps non-greedy matching
: : could also terminate the token prefix.
:
: Well, that's more or less arguing it the other way.
On Thu, Sep 06, 2007 at 04:02:19PM -0500, Patrick R. Michaud wrote:
: I agree. One thought I had was that perhaps non-greedy matching
: could also terminate the token prefix.
Well, that's more or less arguing it the other way. It kind of assumes
your fooba-ish arguments are smart enough to test
On Thu, Sep 06, 2007 at 01:40:20PM -0700, Jonathan Lang wrote:
: So 'orelse' is exactly like '//', except that the result of the left
: side gets passed to the right side as an error message. Is there a
: reason to make this exception, as opposed to altering '//' to behave
: exactly like 'orelse'
On Thu, Sep 06, 2007 at 12:37:37PM -0700, Larry Wall wrote:
> On Thu, Sep 06, 2007 at 01:25:12PM -0500, Patrick R. Michaud wrote:
> : On a somewhat similar question, what happens with a pattern
> : such as
> :
> : "foobar" ~~ / foo.+? | fooba /
> :
> : The LHS initially matches "foob", but wi
So 'orelse' is exactly like '//', except that the result of the left
side gets passed to the right side as an error message. Is there a
reason to make this exception, as opposed to altering '//' to behave
exactly like 'orelse' does?
--
Jonathan "Dataweaver" Lang
On Thu, 2007-09-06 at 12:37 -0700, Larry Wall wrote:
> Yow. ICATBW.
The what now?
-'f
On Thu, Sep 06, 2007 at 01:25:12PM -0500, Patrick R. Michaud wrote:
: > Were we using the procedural conjunction:
: >
: > "foobar" ~~ / <[a..z]>+ && [ ... ] /;
: >
: > I would guess that the LHS matches as much as it can ("foobar"), then
: > the RHS matches "foo" [...and then backtracks the L
On Wed, Sep 05, 2007 at 09:36:24PM -0500, Jonathan Scott Duff wrote:
> How do C<&> and C<&&> differ with respect to backtracking? For instance,
>
> "foobar" ~~ / <[a..z]>+ & [ ... ] /;
>
> Both sides of the C<&> happen in parallel, so I would guess that they
> both match "foo" then stop. Ple
Author: larry
Date: Thu Sep 6 09:51:18 2007
New Revision: 14448
Modified:
doc/trunk/design/syn/S03.pod
Log:
brainos
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod(original)
+++ do
Author: larry
Date: Thu Sep 6 09:31:16 2007
New Revision: 14447
Modified:
doc/trunk/design/syn/S03.pod
Log:
Add logic programming primitives with decent binding of intermediate state
The much-despised "err" operator is gone; use "orelse" instead
Modified: doc/trunk/design/syn/S03.pod
==
> You've done a lot of work on this in parrot already and I haven't seen
> anything new as far as attributes go for a while. Have you finished
> adding gcc attributes? If so, we can close this ticket.
On attributes, I think so. Warning flags will be a separate project.
--
Andy Lester => [EMAI
You've hit different child processes.
"James E Keenan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Jeff Horwitz wrote:
> >
>
> > Counter: http://www.smashing.org/sandbox/perl6-handlers/counter
> >
> >
>
> When I first clicked on this link, the counter stood at 30. Then, when
> I
Friends:
Parrot::Configure::Step holds an internal subroutine called
_run_command() whose task is to execute a system call on a command
supplied as an argument. The command supplied is typically a small
C-executable created on the fly as a particular configuration step runs.
I've been stari
Jeff Horwitz wrote:
Counter: http://www.smashing.org/sandbox/perl6-handlers/counter
When I first clicked on this link, the counter stood at 30. Then, when
I hit the Refresh button, it surprised me by jumping directly to 45.
Subsequent refreshes incremented the counter by 1, as I would
Jonathan Scott Duff wrote:
> How do C<&> and C<&&> differ with respect to backtracking? For instance,
>
> "foobar" ~~ / <[a..z]>+ & [ ... ] /;
>
> Both sides of the C<&> happen in parallel, so I would guess that they
> both match "foo" then stop. Please correct me if that's wrong.
As written,
On 05/09/07, Jeff Horwitz <[EMAIL PROTECTED]> wrote:
> It gives me great pleasure to introduce you to the world's first mod_perl6
> handlers! They are run using Parrot's Perl6 compiler on top of
> mod_parrot, and are compiled on the fly the first time a handler is
> called. Each handler is passed
On Fri May 05 15:18:22 2006, petdance wrote:
>
> GCC has a number of attributes that we can slap on functions. For
> example, GCC's analysis of flow control will be greatly improved when
> we put __attribute(noreturn)__ on real_exception(), to tell GCC that
> it can't return, like exit().
>
> thanks for the quick turnaround. this test is perfect for the
> 'executed from pir test case', and will be applied shortly.
The test case has been added in r21092.
> but as
> patrick later provided an example of executing a .pbc file, we'll also
> need a test for this before the ticket is close
How do C<&> and C<&&> differ with respect to backtracking? For instance,
"foobar" ~~ / <[a..z]>+ & [ ... ] /;
Both sides of the C<&> happen in parallel, so I would guess that they
both match "foo" then stop. Please correct me if that's wrong.
Were we using the procedural conjunction:
"
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #45209]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45209 >
Parrot is supposed to follow IEEE conventions for truth. 0.0 and -0.0 are
false, NaN is
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #45217]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45217 >
More clean-up of Class to 'Class' in t/op, t/library and t/compilers.
Index: t/compiler
It gives me great pleasure to introduce you to the world's first mod_perl6
handlers! They are run using Parrot's Perl6 compiler on top of
mod_parrot, and are compiled on the fly the first time a handler is
called. Each handler is passed an [Apache;RequestRec] object instantiated
by mod_parrot
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #45203]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45203 >
t/examples/tutorial.t is passing, but should not be due to a parrot bug. -0.0
is suppo
38 matches
Mail list logo
