On Wed May 28 18:26:48 2008, [EMAIL PROTECTED] wrote:
> On Wednesday 28 May 2008 18:15:32 James Keenan via RT wrote:
>
> > Yes. That worked. Thanks for the suggestion. Please see revised
> patch
> > attached.
>
> All tests pass for me, so +1 here. I say commit away.
+1.
Committed as r28020
On Wednesday 28 May 2008 18:15:32 James Keenan via RT wrote:
> Yes. That worked. Thanks for the suggestion. Please see revised patch
> attached.
All tests pass for me, so +1 here. I say commit away.
I do have one more question though:
> +{
> + my $tdir = tempdir();
> + foreach my $g (
On Wed May 28 10:25:09 2008, [EMAIL PROTECTED] wrote:
>
> Okay, that's fixable. If you *really* need to optimize this regex,
> use qr//,
> as it generally works better than /o.
[snip]
>
> Can you combine the test files then?
>
Yes. That worked. Thanks for the suggestion. Please see revis
On Wednesday 28 May 2008 04:37:43 James Keenan via RT wrote:
> On Tue May 27 20:23:21 2008, [EMAIL PROTECTED] wrote:
> > Why are there four separate test files? It makes more sense to me to
> > combine them into a single test file; I'm not sure why there's such a
> > proliferation of multiple te
On Tue May 27 20:23:21 2008, [EMAIL PROTECTED] wrote:
> Why are there four separate test files? It makes more sense to me to
> combine
> them into a single test file; I'm not sure why there's such a
> proliferation
> of multiple test files for files being tested.
>
Since the usage of the progra
On Tuesday 27 May 2008 20:06:29 James Keenan via RT wrote:
> Here's a patch with the requested conversion to Perl.
>
> Since this program is really a Parrot developer's tool, I'm recommending
> that it be moved to tools/dev/ from tools/docs/.
>
> Much of the functionality has been extracted into s
Here's a patch with the requested conversion to Perl.
Since this program is really a Parrot developer's tool, I'm recommending
that it be moved to tools/dev/ from tools/docs/.
Much of the functionality has been extracted into subroutines imported
from lib/Parrot/SearchOps.pm. Tests of those subr
On Thu May 01 17:29:58 2008, [EMAIL PROTECTED] wrote:
>
> I believe that you give it the name of an opcode, and it tells you which
> src/ops/*.ops file contains it and any documentation for that opcode.
>
> I'd use it, if it worked.
>
It does work, but only when called from the directory in
On Thursday 01 May 2008 15:51:17 James Keenan via RT wrote:
> *Is* the script worth keeping? If someone can describe how it is
> useful, then I will take a crack at perl-izing it.
I believe that you give it the name of an opcode, and it tells you which
src/ops/*.ops file contains it and any doc
On Thu May 01 11:20:22 2008, coke wrote:
> We shouldn't rely on having python available to developers. If this
> script is worth keeping, it should be converted to perl.
>
*Is* the script worth keeping? If someone can describe how it is
useful, then I will take a crack at perl-izing it.
kid51
# New Ticket Created by Will Coleda
# Please include the string: [perl #53602]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53602 >
We shouldn't rely on having python available to developers. If this
script is worth keepi
11 matches
Mail list logo
