This new test is looking rather poorly. The main problem seems to be that runperl returns the expected lines of data but not in the expected order. Details below. I haven't had time to see if anything can be done about it, so for now this is just a bug report.
$ perl [-.ext.b.t]o.t 1..9 ok 1 - require O not ok 2 - O.pm should not munge perl output without -qq # Failed at [-.ext.b.t]o.t;-0 line 33 # got 'Compiling!' # expected '-e syntax OK' not ok 3 - Output should not be saved without -q switch # Failed at [-.ext.b.t]o.t;-0 line 34 # got '(foo) <bar>' # expected 'Compiling!' not ok 4 - O.pm should call backend compile() method # Failed at [-.ext.b.t]o.t;-0 line 35 # got '[]' # expected '(foo) <bar>' not ok 5 - Nothing should be in $O::BEGIN_output without -q # Failed at [-.ext.b.t]o.t;-0 line 36 # got '-e syntax OK' # expected '[]' ok 6 - Output should not be printed with -q switch not ok 7 - ... but should be in $O::BEGIN_output # Failed at [-.ext.b.t]o.t;-0 line 45 # got ']' # expected '[Compiling!' ok 8 - -qq should suppress even the syntax OK message not ok 9 - O.pm should die if backend compile() does not return a subref # Failed at [-.ext.b.t]o.t;-0 line 54 # got 'Compiling!' # expected /(?-xism:fail at .eval)/ $ -- ____________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "Literary critics usually know what they're talking about. Even if they're wrong." -- Perl creator Larry Wall
