Shlomi Fish writes:
On Wednesday 02 November 2005 08:23, Michael G Schwern wrote:
Given that the existing interface is pretty simple, I really don't
see why one has to completely fork the code base just to put on a
new interface. Surely any new code with a fancy new interface can
On Wednesday 02 November 2005 08:23, Michael G Schwern wrote:
On Tue, Nov 01, 2005 at 03:16:01PM +0200, Shlomi Fish wrote:
I'd like to see
that sort of thing as patches to Test::Harness rather than in a fork.
Well, I started with Test::Harness and gradually revamped it. The problem
is
On Tue, Nov 01, 2005 at 03:16:01PM +0200, Shlomi Fish wrote:
I'd like to see
that sort of thing as patches to Test::Harness rather than in a fork.
Well, I started with Test::Harness and gradually revamped it. The problem is
that some aspects of the T::H interface suck, and I had to
Hi Michael!
Thanks for your commentary.
On Monday 10 October 2005 23:27, Michael G Schwern wrote:
On Mon, Oct 10, 2005 at 10:53:34PM +0200, Shlomi Fish wrote:
Let me know what you think.
$ perl -Ilib -wle 'use Test::Shlomif::Harness::Obj;
In article [EMAIL PROTECTED], Andy Lester
[EMAIL PROTECTED] wrote:
On Mon, Oct 10, 2005 at 02:52:49PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
I do NOT want to see that sort of thing as patches to Test::Harness.
I have a few ideas myself on how to make T::H a little more clean and
Since this is a community, you can also work with
him to make it all work out.
Shlomi and I have already discussed this.
I don't think anyone should have to get
anyone's permission to play with open source code.
That's exactly right, they don't, and I would never presume to tell
them
On Monday 10 October 2005 23:41, Andy Lester wrote:
On Mon, Oct 10, 2005 at 02:27:03PM -0700, Michael G Schwern
([EMAIL PROTECTED]) wrote:
The way you've broken down the nattier bits of Test::Harness, such as
_show_results(), into digestable functions has value. I'd like to see
that sort
Andy Lester [EMAIL PROTECTED] wrote:
The real issue is that, if Shlomi had come to me and discussed the
issues rather than I want to fork Test::Harness, we could have worked
together. Instead, it's I want color-coding of tests, and T::H doesn't
do what I want, so I'm gonna go fork it, OK?
Andy Lester wrote in perl.qa :
On Mon, Oct 10, 2005 at 02:52:49PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
I do NOT want to see that sort of thing as patches to Test::Harness.
I have a few ideas myself on how to make T::H a little more clean and
useful, but I'd have to do some
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
That said, now that TAP is well documented (yay), there's nothing wrong
with writing other harnesses.
Just as a comment, I used the TAP doco to write a VB console app for
testing the non-GUI (library) part of a VB
On Mon, Oct 10, 2005 at 10:53:34PM +0200, Shlomi Fish wrote:
Let me know what you think.
$ perl -Ilib -wle 'use Test::Shlomif::Harness::Obj;
Test::Shlomif::Harness::Obj-new-runtests(test_files = [EMAIL PROTECTED])'
t/*.t
Can't use an undefined value as an ARRAY reference at
On Mon, Oct 10, 2005 at 02:27:03PM -0700, Michael G Schwern ([EMAIL PROTECTED])
wrote:
The way you've broken down the nattier bits of Test::Harness, such as
_show_results(), into digestable functions has value. I'd like to see
that sort of thing as patches to Test::Harness rather than in a
On Mon, 2005-10-10 at 16:41 -0500, Andy Lester wrote:
I do NOT want to see that sort of thing as patches to Test::Harness.
I would like anyone who presumes that he's going to change the internals
of a module I maintain to talk to me about a general overview of the
changes first, rather than
On Mon, Oct 10, 2005 at 02:52:49PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
I do NOT want to see that sort of thing as patches to Test::Harness.
I have a few ideas myself on how to make T::H a little more clean and
useful, but I'd have to do some refactorings myself on a private fork to
On Mon, 2005-10-10 at 17:22 -0500, Andy Lester wrote:
The real issue is that, if Shlomi had come to me and discussed the
issues rather than I want to fork Test::Harness, we could have worked
together. Instead, it's I want color-coding of tests, and T::H doesn't
do what I want, so I'm gonna
On Mon, Oct 10, 2005 at 03:38:20PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
I agree that his approach was inappropriate. Still, he has working code
and that's significant.
http://petdance.com/perl/geek-culture/
I don't think Shlomi's a fuckhead, nor do I have the bozo bit flipped
against
16 matches
Mail list logo
