Hi all,

Schwern and I have been discussing TAP 2.0 and barring objections, we
like the diagnostic syntax proposed in
http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax.

However, there's one area that we're less clear on and the following
two suggestions are bantered about:

    not ok 1 - differences in text
    file:     (eval 2)
    line:     14
    name:     differences in text
    got:      this is line 1
              this is line 2
              this is line 3
    expected: this is line 1
              this is line b
              this is line 3
    display:  +---+----------------+----------------+
              | Ln|Got             |Expected        |
              +---+----------------+----------------+
              |  1|this is line 1  |this is line 1  |
              *  2|this is line 2  |this is line b  *
              |  3|this is line 3  |this is line 3  |
              +---+----------------+----------------+

Versus:

    not ok 1 - differences in text
    file:  (eval 2)
    line:  14
    name:  differences in text
    got:   <<END
    this is line 1
    this is line 2
    this is line 3
    END
    expected: <<END
    this is line 1
    this is line b
    this is line 3
    END
    display: <<END
    +---+----------------+----------------+
    | Ln|Got             |Expected        |
    +---+----------------+----------------+
    |  1|this is line 1  |this is line 1  |
    *  2|this is line 2  |this is line b  *
    |  3|this is line 3  |this is line 3  |
    +---+----------------+----------------+
    END

Naturally, we have our respective opinions about the merits of this,
but we're willing to be pursuaded that one of us is wrong.

There are all sorts of little details there, but basically,
got/expected (or whatever names are settled on) are to be free-form
text.  The main question is whether or not those forms are HERE docs or
follow a pseudo-YAML convention).

Cheers,
Ovid

--

Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Reply via email to