On Wed Sep 17 05:30:18 2008, [EMAIL PROTECTED] wrote:
> >
> > 4. I will then open up a new RT of the [RFC] class. This ticket will
> > call for development of a specification of a way to visually display the
> > extent to which Parrot's tests cover the specification. I'll be quoting
> > from p
# New Ticket Created by James Keenan
# Please include the string: [perl #58990]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58990 >
We need a way to measure the extent to which Parrot's test suite covers
the Parrot speci
http://www.parrotcode.org/release/devel still points to 0.7.0
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
On Wed, Sep 17, 2008 at 08:08:47PM +0200, Reini Urban wrote:
> http://www.parrotcode.org/release/devel still points to 0.7.0
I sent the appropriate patch to the webmaster, but it hasn't
been applied yet (and I lack a commit bit for the parrotcode.org site).
Once that's applied, the url should be f
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58980]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58980 >
As suggested by Allison, in a .begin/end_return sequence, the .return
directive will b
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58974]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58974 >
as suggested by Allison,
.return in a tailcall context, like this:
.return foo()
wi
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58976]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58976 >
as suggested by Allison, the .arg directive in a .begin_call/end_call
statement will b
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58978]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58978 >
as suggested by Allison, .result in a .begin/end_call sequence will be
replaced by .ge
On Tue, Sep 16, 2008 at 11:45 PM, Christoph Otto via RT
<[EMAIL PROTECTED]> wrote:
> On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote:
>> On Tuesday 16 September 2008 14:47:58 NotFound wrote:
>>
>> > > It certainly shouldn't segfault. But, the question is: why does it
>> > > segfault at 206 par
On Wed, Sep 17, 2008 at 10:57:31AM +0200, Allison Randal wrote:
> Patrick R. Michaud wrote:
>>
>> I'm not sure about this last comment -- I think I can imagine
>> that other language implementations (including new ones we haven't
>> thought of yet but suddenly becomes possible with Parrot) might wa
Patrick R. Michaud a écrit :
On behalf of the Parrot team, I'm proud to announce Parrot 0.7.1
"Manu Aloha." Parrot (http://parrotcode.org/) is a virtual machine aimed
at running all dynamic languages.
As usual, the Windows setup is available on
http://parrotwin32.sourceforge.net/
François.
On Wednesday 17 September 2008 04:48:59 [EMAIL PROTECTED] (via RT) wrote:
> src/exceptions.c(74): error: identifier "_CONST_STRING_74" is undefined
> VTABLE_set_integer_keyed_str(interp, exception,
This one means that ICC handles #line directives differently. If you manually
edit this lin
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #58958]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58958 >
I'm trying to build Parrot 0.7.1 with Intel Compiler (see version
information below
On Tue Sep 16 15:45:47 2008, [EMAIL PROTECTED] wrote:
>
> 2. I will apply a refined version of the patch. It will delete inline
> comments referring to the deleted tickets. But I will leave to others
> dealing with reference to smartlinks under languages/.
Done, now that release has been cut.
Not long ago, Patrick R. Michaud proclaimed...
> I'm not sure about this last comment -- I think I can imagine
> that other language implementations (including new ones we haven't
> thought of yet but suddenly becomes possible with Parrot) might
> want to make use of gather/take semantics if they'
On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote:
> On Tuesday 16 September 2008 14:47:58 NotFound wrote:
>
> > > It certainly shouldn't segfault. But, the question is: why does it
> > > segfault at 206 parameters? Throwing an exception to avoid an
> error we
> > > don't understand isn't good
On Mon Sep 15 20:08:38 2008, [EMAIL PROTECTED] wrote:
> chromatic wrote:
> > On Monday 15 September 2008 01:25:15 Christoph Otto via RT wrote:
> >
> >> It applies with a little noise to the current trunk and passes make
> >> test. The attached version just changes line numbers so the patch
> >> ap
Bob Rogers wrote:
Yes, once we have the ability to have exception handlers only handle
specific types of exceptions, then they'll allow all other types of
exceptions to pass through. (Which means we won't end up with the
infinite exception handler loops we currently get if excepti
Patrick R. Michaud wrote:
I'm not sure about this last comment -- I think I can imagine
that other language implementations (including new ones we haven't
thought of yet but suddenly becomes possible with Parrot) might
want to make use of gather/take semantics if they're readily available --
e
19 matches
Mail list logo
