> I thought of an alternative which might have a number of the benefits of
> this solution with less of the drawbacks.
>
> The idea is to create one big file test file that is run in the normal
> way. Everything would only need to be loaded once instead of N times.
> There wouldn't be the usual pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In addition to the shootout machine, I have a main development box
that runs Mac OS X (PowerPC). I attempted to build Parrot 0.4.0 on
this machine and encountered errors. The mailing list archive seems
to be down at the moment, so I could not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
A long while back someone made a request for people to create parrot
implementations of the shootout tests on Alioth (http://
shootout.alioth.debian.org). I wanted to let you know that I have
updated the shootout build machine with parrot (
On Wed, Dec 07, 2005 at 08:01:39PM +, Mark Stosberg wrote:
> So I'm now using and liking Selenium after several recommendations from
> this list. I'm interested to know how other people integrate it with a
> traditional perl test suite. It seems like there are two possibilities:
>
> http://s
The change below means that the following code no longer works for
loading non-Parrot compiled libraries from the current directory:
load_bytecode "structures.pbc"
Must I specify an absolute pathname to get the original behavior?
-- Bob Rogers
On Wed, Dec 07, 2005 at 05:17:23PM -0800, Allison Randal wrote:
> >But at the moment, a string can be matched based on balanced and
> >nested parentheses using
> >
> >
>
> Ah-ha! This works:
>
> p6rule('\d+ | ', 'PunieGrammar', 'term')
>
> (I experimented with several variations of syntax
On Dec 7, 2005, at 15:34, Patrick R. Michaud wrote:
For this I was following the design of "extract_bracketed" in
Perl 5's Text::Balanced, which returns the delimiters as part
of the string. I agree it would be nice for PGE::Text::bracketed
to also return the string without the outer delimiters
On 2005-12-07, Mark Stosberg <[EMAIL PROTECTED]> wrote:
>>
>> Limitations and Caveats with the system:
>>
>> * Scripts that muck about with STDIN, STDOUT or STDERR will probably
>>have problems.
>>
>> * The usual persistent environment caveats apply: be careful with
>>redefined subs, glo
On Wed, Dec 07, 2005 at 03:17:10PM -0800, Allison Randal wrote:
> On Oct 17, 2005, at 14:15, Patrick R. Michaud wrote:
>
> >I've just added a subrule to PGE,
> >which is roughly analogous to the "bracketed" function in
> >Perl 5's Text::Balanced.
> >
>
> Shouldn't it contain C? That is, shouldn'
On Oct 17, 2005, at 14:15, Patrick R. Michaud wrote:
I've just added a subrule to PGE,
which is roughly analogous to the "bracketed" function in
Perl 5's Text::Balanced.
Like most PGE subrules, PGE::Text::bracketed can be called
as a subrule in a rule expression or directly via a subroutine ca
On 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. this should be grouped with other compiler/-related
> modifications.
> Note: see the parent ticket for more information.
>
RT is still down. so, i'll c
Hello,
So I'm now using and liking Selenium after several recommendations from
this list. I'm interested to know how other people integrate it with a
traditional perl test suite. It seems like there are two possibilities:
http://selenium.thoughtworks.com/
1. Use "prove" as the primary test sui
On 2005-12-05, Michael Graham <[EMAIL PROTECTED]> wrote:
>
> This should be compatible with regular (non-PersistentPerl) use as well.
>
> ...
>
> Limitations and Caveats with the system:
>
> * Scripts that muck about with STDIN, STDOUT or STDERR will probably
>have problems.
>
> * The usual p
On Dec 6, 2005, at 16:08, jerry gay wrote:
On 12/6/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
2) I'm very much inclined to remove the Win32 special casing (see also
r8673)
There are already 2 possibilities to specify the runtime prefix (where
libs are searched).
a) perl Configure --prefix
On Tue, 2005-12-06 at 20:26 -0500, Michael Cummings wrote:
> I realize I'm talking to myself at this point (last post, promise), but
> my last message failed to explain the paste at the top. On a box without
> svk, using the 0.4.0 released tarball, all is fine (t/perl/manifest.t is
> skipped/faile
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Wed, 7 Dec 2005 12:44:32 +0100
On Dec 7, 2005, at 5:39, Bob Rogers wrote:
> Turns out this is because of "premature optimization"
Argh - sorry. That shouldn't have been on of course. I did some
benchmarking and must have forgotte
On Dec 7, 2005, at 2:26, Michael Cummings wrote:
I realize I'm talking to myself at this point (last post, promise), but
my last message failed to explain the paste at the top. On a box
without
svk, using the 0.4.0 released tarball, all is fine (t/perl/manifest.t
is
skipped/failed quickly).
On Dec 7, 2005, at 5:39, Bob Rogers wrote:
Turns out this is because of "premature optimization"
Argh - sorry. That shouldn't have been on of course. I did some
benchmarking and must have forgotten to disable it. It is ment to
access the signature array faster. The type of the signature arr
Discussions about module versions have touched on questions of how to
distinguish or specify interfaces/APIs a few times, but I haven't
seen much detail, so I thought I'd post some musings on the subject.
At its simplest, I want to add some functionality to my program by
using some module; and
HaloO,
Larry Wall wrote:
My gut-level feeling on this is that $! is going to end up being an
"env" variable like $_.
I just re-read about exceptions. Well, I undestand now that $! is
intented as a variable with a spectrum of meanings ranging from
1) the return value of a sub, through
2) a
20 matches
Mail list logo
