# New Ticket Created by Will Coleda
# Please include the string: [perl #33923]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33923 >
Dan says:
Let's add it as a TODO. Two new interpinfo options -- fullname (which gives t
From the ROADMAP -
=head1 NEXT RELEASE (0.1.2)
This release has a ticket opened as [perl #33916].
http://rt.perl.org/rt3/Ticket/ModifyLinks.html?id=33916
has a list of all the open issues which must be completed for this release.
-snip-
I insured the major items you mentioned were listed as childre
# New Ticket Created by Will Coleda
# Please include the string: [perl #33922]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33922 >
Leo is working on a generational GC system, which needs to be committed.
# New Ticket Created by Will Coleda
# Please include the string: [perl #33921]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33921 >
Dan is in progress on a substantial revision to the string code which needs to
be re-in
# New Ticket Created by Will Coleda
# Please include the string: [perl #33920]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33920 >
PDD13 (Bytecode) must be completed.
# New Ticket Created by Will Coleda
# Please include the string: [perl #33919]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33919 >
PDD12 (Assembly) must be completed.
# New Ticket Created by Will Coleda
# Please include the string: [perl #33918]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33918 >
PDD 10 (Embedding) must be completed.
# New Ticket Created by Will Coleda
# Please include the string: [perl #33917]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33917 >
PDD05 (Opcode Function specs) - Per Leo, this document is obsolete and must be
re-imple
This is now moved and updated.
No cvs magic was used in the relocation of this file.
William Coleda wrote:
If it's an example, let's move it to "example/c/test_main.c", then, and
update the comment in the beginning of the file that says:
=head1 DESCRIPTION
THIS FILE IS NO LONGER USED.
with your n
# New Ticket Created by Will Coleda
# Please include the string: [perl #33916]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33916 >
This is a placeholder ticket for the 0.1.2 release.
I have isolated a case where perl is happy but D::C segfaults
sort.pl
#!/usr/bin/perl -w
use strict;
my %sort = (B => \&backwards,
F => \&forwards);
sub backwards {
return $b cmp $a;
}
sub forwards {
return $a cmp $b;
}
sub GetAlgorithm {
my ($alg)
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #33915]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=33915 >
Parrot IO needs some work. The documentation for the read opcode
(docs/ops/io.pod) c
Hi Ian,
Test::Unit was a nice idea, but it's been abandoned.
Test::Inline seems nice, but it doesn't give you the full benefits of
Test::Class (convenient setup, teardown, inheritance, etc.).
Test::Class is great. I'm quite happy with it. If you're more
comfortable with XUnit style testing, th
Hi all,
Long before prove came along, I used a program named "grind" to manage
my test suites. One thing that grind had that prove does not was the
ability to specify *which* tests to run. grind did it via shell
expansion and that was terrible. Andy sensibly did not include that in
prove.
I wa
I'm taking a software development class this semester which will involve
writing extensive object-oriented code. My partner and I are trying to
decide whether to use Test::Unit, ::Class, or ::Inline for our test scripts.
I can see the advantages of Test::Class in terms of object heirarchy,
but
Per this message from Schwern
(http://www.mail-archive.com/perl-qa@perl.org/msg03122.html) on how to
trigger custom behavior for individual tests:
For individual failures, put a wrapper around
Test::Builder->ok(). Use Hook::LexWrap, Sub::Uplevel
or Aspects to preserve the call stack.
Well
"Andy Lester" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There's a new Phalanx article on perl.com:
> http://www.perl.com/pub/a/2005/01/13/phalanx.html
>
> Let's hope we get an influx of Hoplites!
>
> xoxo,
> Andy
>
Hey Andy,
I am new to Perl. If you went by the "Perl Medic" bo
William Coleda <[EMAIL PROTECTED]> wrote:
> What needs to be completed to cut 0.1.2 ? (0.1.1 was cut > 100 days ago)
Yeah. 0.1.2 should be out in about 2 weeks. It should contain:
- Dan's unicode string changes
I'd be happy if people check out that branch and test it.
Merging the branch back
18 matches
Mail list logo
