On Tue, Mar 01, 2005 at 11:06:17PM -0600, Rod Adams wrote:
: Since the line between rules and subs is already blurring significantly,
: I want to blur it a little more. I want to write rules which can take
: parameters.
No problem. That's how the arguments to rules like are
already passed. If
file: $CPAN/authors/id/P/PE/PETDANCE/Test-Harness-2.47_02.tar.gz
size: 64982 bytes
md5: a9698f7e608a72650fee33d25a08506b
I'm starting the infrastructure of having Test::Harness::Point objects
in the straps, so that calling programs can access the test line
properties however they choose.
Rod Adams writes:
> Since the line between rules and subs is already blurring significantly,
> I want to blur it a little more. I want to write rules which can take
> parameters.
No no no! That's too powerful.
Wow, skimming through both S5 and A5 and I see no mention of such a
thing. I know w
Since the line between rules and subs is already blurring significantly,
I want to blur it a little more. I want to write rules which can take
parameters.
Consider that I am parsing HTML (a very frequent occurrence), and wish
to make a Rule that matches a balanced tag from open to close. I wa
On Sun, Feb 27, 2005 at 10:52:58AM -0800, Dave Whipp wrote:
: One could imagine implementing this by creating the scopes as instances
: of an object, and then binding the object's attributes onto the
: variables (i.e. "our $foo := $obj.bar"). The "scope space" object would
: then be the set of g
On Tue, Mar 01, 2005 at 07:52:24PM -0500, Abhijit Mahabal wrote:
>
> In general, is this the right place to send pugs bug reports?
Unless/until Autrijus says otherwise, this is a terrific
place to send pugs bug reports.
Pm
I had not realized that "foo".say is valid p6 :)
Is "foo" .say also valid p6? No reason for it not to be valid
Pugs currently works with the non-space version, but barfs at the space
version...
In general, is this the right place to send pugs bug reports?
--abhijit
Alex Burr writes:
> On Sun, Feb 27, 2005 at 03:36:42PM -0700, Luke Palmer wrote:
> > But the biggest problem is that if the user overloads 'equal' on two
> > objects, the hash should consider them equal. We could require that to
> > overload 'equal', you also have to overload .hash so that you've
Autrijus Tang wrote:
On Sun, Feb 27, 2005 at 04:14:34PM -0500, Abhijit Mahabal wrote:
I hunted down the cause of the non-parsing of
ok((2 + 3) == $five, "== (sum on lhs)");
in 03operator.t, but am not yet up to speed in Haskell to fix it.
Below is the location of the problem.
The error is in Parse
On Sun, Feb 27, 2005 at 03:36:42PM -0700, Luke Palmer wrote:
> But the biggest problem is that if the user overloads 'equal' on two
> objects, the hash should consider them equal. We could require that to
> overload 'equal', you also have to overload .hash so that you've given
> some thought to th
Michael G Schwern wrote:
Is it possible to standardize this, so a generic harness knows
which test a comment line acctually describes?
I'm going to call a big, fat YAGNI on this one for the time being. It
requires a change to both the protocol and testing libraries for a minimal
organizational im
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> with 'make testr' I get a single test failure. My guess is that the
> string encoding is not properly written to the dumped PBC file:
Fixed.
leo
12 matches
Mail list logo
