Andy,
Thanks for the bug report! This is good info to know :-)
> A nightly cvs update and make smoke and I've been seeing failures for
> about a week. I tried parrotbug but got no response. Here's the failing
> call
Have you been using the parrotbug script? If so, it is known that it
doesn't
# New Ticket Created by Jeff Horwitz
# Please include the string: [perl #45787]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45787 >
make -j N has failed for some time. the attached patch fixes the problem
by synchronizi
On 26/09/2007, chromatic <[EMAIL PROTECTED]> wrote:
> On Wednesday 26 September 2007 01:16:54 [EMAIL PROTECTED] wrote:
>
> > Author: paultcochrane
> > Date: Wed Sep 26 01:16:53 2007
> > New Revision: 21597
> >
> > Modified:
> >trunk/languages/m4/src/eval.c
> >
> > Log:
> > [m4] Cast isxxx() fun
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #45783]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45783 >
A nightly cvs update and make smoke and I've been seeing failures for
about a week
> http://smoke.parrotcode.org/smoke/
>
Is the code that generates this page publicly available?
If it is, I'd like to take a look at it.
thanks.
kid51
To summarize a bit of off-line correspondence with Allison and chromatic:
Allison wrote today:
"I can see why the [configuration step] object would be useful for
retrieving more information. In fact, the whole question of success,
failure, and whether the step should be fatal could be stored i
Allison has pointed out one error in the part of the patch referring to
lib/Parrot/Configure.pm. This comment, which describes what happens
*some* of the time when a particular config step DWIMs, should have been
deleted.
# When successful, a Parrot configuration step returns itself,
On Wednesday 26 September 2007 14:26:20 [EMAIL PROTECTED] wrote:
> Author: coke
> Date: Wed Sep 26 14:26:19 2007
> New Revision: 21613
>
> Modified:
>trunk/lib/Parrot/Configure/Messages.pm
>trunk/tools/build/c2str.pl
>
> Log:
> [build]
>
> Update c2str.pl so that multiple copies running si
Patrick R. Michaud wrote:
This ended up being discussed on IRC -- just to complete this thread
I'll note that we settled on the 'typeof' opcode to return the
class (or PMCProxy) object for a PMC:
$P1 = typeof $P0# $P1 is class object / PMC proxy of $P0
And committed on the pdd15oo bra
Author: larry
Date: Wed Sep 26 13:46:07 2007
New Revision: 14465
Modified:
doc/trunk/design/syn/S02.pod
Log:
Renamed .bit to .true
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod(or
On Wed, Sep 26, 2007 at 01:57:10PM -0500, Patrick R. Michaud wrote:
> On Wed, Sep 26, 2007 at 01:39:51PM -0500, Patrick R. Michaud wrote:
> > This is primarily for Allison, but others can chip in
> >
> > 1. In PIR, if I have an Object in a PMC register, how do I
> > determine its correspo
On Wed, Sep 26, 2007 at 01:39:51PM -0500, Patrick R. Michaud wrote:
> This is primarily for Allison, but others can chip in
>
> 1. In PIR, if I have an Object in a PMC register, how do I
> determine its corresponding Class object? Is the "standard"
> mechanism to use the C opcode?
>
This is primarily for Allison, but others can chip in
1. In PIR, if I have an Object in a PMC register, how do I
determine its corresponding Class object? Is the "standard"
mechanism to use the C opcode?
$P1 = inspect $P0, 'class' # $P1 is class object of $P0
2. W
On Wednesday 26 September 2007 01:16:54 [EMAIL PROTECTED] wrote:
> Author: paultcochrane
> Date: Wed Sep 26 01:16:53 2007
> New Revision: 21597
>
> Modified:
>trunk/languages/m4/src/eval.c
>
> Log:
> [m4] Cast isxxx() function arguments explicitly to unsigned char as per
> coding standards.
I
On 9/16/07, Allison Randal <[EMAIL PROTECTED]> wrote:
>
> Klaas-Jan Stol (via RT) wrote:
> >
> > I propose to change this into:
> >
> > HLL_map "Integer", "TclNumber"
>
> Agreed and approved.
This variant is now implemented (r21601). The docs (imcc/syntax.pod) is
updated, and the INTC variant is
15 matches
Mail list logo
