----- Original Message ---- From: Andy Armstrong <[EMAIL PROTECTED]> > I've updated it with that text :)
Thanks! I still feel that my copy was awkward, so if you have a better way of writing it, that's fine. In other news, still working on my presentation. (http://vienna.yapceurope.org/ye2007/talk/475) Here's my basic plan: * Show version 1 of TAP. * Quickly (one slide per second), whip through the next twelve versions. * Compare the version 1 grammar to the version 13 grammar [1] * TAP is evolving faster than the parsers * Why not refactor Test::Harness? * Test::Harness RT queue * Show things TAP::Parser can do that Test::Harness cannot (or is clumsy at) [2] - TODO and SKIP identification - TODO and SKIP lists (--directives) - Colored test output - GUIs (anyone want to fix the GTK GUI?) - Failures only - Callback actions - Improved diagnostics - Multi-language test suites * To Test::Harness 3.0 and beyond - Improve test coverage - Improve documenation - Parallel tests * TAP::Parser internals I would love feedback on any and all of this. Cheers, Ovid [1] The version 1 grammar looks like this (simplified): tap ::= plan "\n" lines plan ::= '1..' posInteger lines ::= line {line} line ::= 'not ' ? 'ok ' posInteger "\n" posInteger ::= ( digit - '0' ) { digit } The version 13 grammar, of course, is at: http://search.cpan.org/dist/TAP-Parser/lib/TAP/Parser/Grammar.pm#TAP_GRAMMAR http://tinyurl.com/yw7t7e [2] Is there anything that Test::Harness can do that TAP::Parser cannot? -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
