# New Ticket Created by "Alek Storm"
# Please include the string: [perl #41549]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41549 >
This patch resolves the problem mentioned in Patrick's replies to
#40626 and #41364 that
On 20/02/07, Will Coleda via RT <[EMAIL PROTECTED]> wrote:
After the application of this test, we have 1265 files that don't pass muster
as of 19FEB2007.
This is related to the new test in t/distro/file_metadata.t right[1]?
In which case this is related to RT#41485. I've set the property
appr
Author: larry
Date: Mon Feb 19 21:53:46 2007
New Revision: 13591
Modified:
doc/trunk/design/syn/S05.pod
Log:
wrong quantifier on ident noted by putter++
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/design/
# New Ticket Created by Will Coleda
# Please include the string: [perl #41548]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41548 >
Failed Test Stat Wstat Total Fail List of Failed
-
The cardinal numbers are most likely all bogus.
I'm surprised that any benchmarks ran at all.
The current cardinal implementation is extremely minimal. Basically
simple arithmetic.
Kevin
Nicholas Clark wrote:
There's a benchmark of Ruby implementations at
http://www.antoniocangiano.com/arti
After the application of this test, we have 1265 files that don't pass muster
as of 19FEB2007.
On Feb 19, 2007, at 11:39 AM, Klaas-Jan Stol wrote:
I'm not sure how to respond on TODO tickets, any pointers would be
appreciated.
Meanwhile, I'll just compose an email, like this one.
Go to RT and Comment on the ticket, CC'ing perl6-internals as
appropriate. Then your comment is logged
There's a benchmark of Ruby implementations at
http://www.antoniocangiano.com/articles/2007/02/19/ruby-implementations-shootout-ruby-vs-yarv-vs-jruby-vs-gardens-point-ruby-net-vs-rubinius-vs-cardinal
(or http://xrl.us/uy5m )
There's a comment from Matt Diephouse
Did you build an optimized ver
Thanks for the head start; now I know to include a test in the future.
Here is an updated version of your patch, with various minor fixes.
On 2/17/07, Allison Randal via RT <[EMAIL PROTECTED]> wrote:
On Sat Jan 27 11:39:15 2007, [EMAIL PROTECTED] wrote:
> This patch allows object vtable method o
James E Keenan wrote:
James Keenan wrote:
# New Ticket Created by James Keenan # Please include the string:
[perl #41455]
# in the subject line of all future correspondence about this issue. #
http://rt.perl.org/rt3/Ticket/Display.html?id=41455 >
Following discussion with particle toda
Author: particle
Date: Mon Feb 19 11:41:15 2007
New Revision: 17067
Modified:
trunk/docs/pdds/draft/pdd15_objects.pod
Log:
[PDD15]: pod fixups
Modified: trunk/docs/pdds/draft/pdd15_objects.pod
==
--- trunk/docs/pdds/d
James Keenan wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #41455]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41455 >
Following discussion with particle today, these patches and new
# New Ticket Created by Joshua Isom
# Please include the string: [perl #41538]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41538 >
If you create a small file, and make sure there is not a newline at the
very
end of the
On Mon, Feb 19, 2007 at 05:39:01PM +0100, Klaas-Jan Stol wrote:
> Ticket:
> #37542: [TODO] core - document behavior of multiple :load subpragmas in
> same compilation unit
> : the behavior of multiple subroutines marked with the ':load' subpragma
> : in the same compilation unit is currently undef
I'm not sure how to respond on TODO tickets, any pointers would be
appreciated.
Meanwhile, I'll just compose an email, like this one.
Ticket:
#37542: [TODO] core - document behavior of multiple :load subpragmas in
same compilation unit
states:
the behavior of multiple subroutines marked with
On Sun, Feb 18, 2007 at 08:38:17PM -0800, jerry gay wrote:
> >> For the moment, disabling configure's manicheck by default would be a
> >> good start.
>
> i don't think manifest checking should be disabled until we have a
> replacement solution in place that makes sure the manifest is checked
> be
This issue was not decided on, and in an attempt to fix this issue, so
this TODO can be closed, a proposition below.
Allison Randal wrote:
Matt Diephouse wrote:
I actually prefer the dot. I don't like the possible ambiguity between
types and local variables:
.local string MyClass
MyClas
Just wanted to make sure everyone was aware of something that
was briefly mentioned during bug day on Saturday...
A last-minute scheduling change means that I'm having to
make a trip out of town tomorrow (Tuesday), which means
that I'll be cutting the Parrot release on Wednesday instead
of tomorro
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Feb 19 14:00:03 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
hi
attached a patch for languages/PIR, fixing:
* added unique_reg to allowed flags for parameters
* updated pirgrammar.pod
* removed pirgrammar.html (can be generated)
* minor fixes for pir.pg (both syntax and comments, now in POD format)
regards,
kjs
Index: languages/PIR/docs/pirgrammar.pod
===
20 matches
Mail list logo