On Fri, Feb 15, 2008 at 10:50:51AM +0100, Rafael Garcia-Suarez wrote:
> On 14/02/2008, Jerry D. Hedden <[EMAIL PROTECTED]> wrote:
> > Change 33313 is causing test suite failures:
> >
> >
> > t/op/pat..FAILED--unexpected
> > output at test 1308
On 15 Feb 2008, at 10:10, Nicholas Clark wrote:
On Fri, Feb 15, 2008 at 10:50:51AM +0100, Rafael Garcia-Suarez wrote:
On 14/02/2008, Jerry D. Hedden <[EMAIL PROTECTED]> wrote:
Change 33313 is causing test suite failures:
t/op/
pat..FAILED--
On 15/02/2008, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> >>> The 'failure' is the extra 'not' before the pound sign.
> >>> I tried to figure out what's causing it, but couldn't.
> >
> > Is it possible to put the TAP parser into a strict mode where it
> > would detect
> > and fault these sor
On 15 Feb 2008, at 10:55, Rafael Garcia-Suarez wrote:
No. Everything is on STDOUT.
Hmm. Hmm again. Yes, I can reproduce that.
print "1..3\n";
print <<'SPLOD';
ok 1 - $+{C} Line 3788
not ok 2 - $+{D} Line 3788 # TODO 1
not # Failed test at line 3788
# expected: 'ḁxfoo'
# result: ''
ok 3
On 15 Feb 2008, at 10:10, Nicholas Clark wrote:
Is it possible to put the TAP parser into a strict mode where it
would detect
and fault these sorts of things?
Yes :)
(well it is now)
Historically we were in the awkward position of trying to fault things
that looked like malformed TAP whi
