so, i think it's best to keep the information as to which tests are
todo and which are skip out of the test data file. currently, this
information exists in the test harness, 'p5rx.t', as i think this is
the best place to capture it. i'm glad to see you've expanded the pge
p5 tests to the full 900+ tests in the file, and i'll gladly apply a
patch that does this while leaving the 're_tests' file intact.
while i'm thinking about it, there should be a better way to reflect
todo or skip reason. if you're up for the challenge, it would be nice
to be able to say something like
my %todo= ( # similar for skip
'not yet implemented' => qw< 5 12 35 500 >,
'broken' => qw< 34 63 11 >,
...
);
and have something that decorates the subtests appropriately. that's
not a requirement for the resubmission of your existing patch, but an
extra request. if it doesn't get done this time around, it will
eventually ;)
~jerry
i think the best way for me to document all this is to write up some
tickets, so i'll be doing that shortly.
~jerry
Did you get around to opening the tickets you mentioned here? If so, I
think we can close this ticket. If not, do you want to sketch out the
ideas for the tickets you want opened? I can then go through the
donkey work of opening them for you if you want.
Paul
My $0.02-
AFAICT, all of the 'todo'/'skip' markers have been factored out of
the p5 and p6 regex test files themselves, so I think it's safe to
close this ticket. Any further improvements to be made to the
tests probably deserve their own tickets, without holding this ticket
open for them.
Pm
Thanks for your help!