Ricardo SIGNES wrote:
> * Michael G Schwern [2009-03-31T18:22:50]
>>> What if display types could be provided informationally in the TAP stream.
>>> The stream could include:
>>>
>>> want: foo bar
>>> have: foo bar
>>> presentation: Some::Plugin
>>>
>>> With the plugin installed, the present
* Michael G Schwern [2009-03-31T18:22:50]
> > What if display types could be provided informationally in the TAP stream.
> > The stream could include:
> >
> > want: foo bar
> > have: foo bar
> > presentation: Some::Plugin
> >
> > With the plugin installed, the presentation layer could fix
David Golden wrote:
> On Tue, Mar 31, 2009 at 6:22 PM, Michael G Schwern wrote:
>> But it's really more useful for more complicated formatting. Something
>> simple
>> like making subtle whitespace differences visible should be a feature of the
>> TAP consumer.
>
> Which is why it will be nice w
# from Michael G Schwern
# on Tuesday 31 March 2009 15:22:
> want: foo bar
> have: foo bar
> display: |
> want: foo\N{SPACE}bar
> have: foo\N{KLINGON MOMENT OF SILENCE}bar
>
>But it's really more useful for more complicated formatting.
> Something simple like making subtle
On Tue, Mar 31, 2009 at 6:22 PM, Michael G Schwern wrote:
> But it's really more useful for more complicated formatting. Something simple
> like making subtle whitespace differences visible should be a feature of the
> TAP consumer.
Which is why it will be nice when the "consumer" isn't just get
Ricardo SIGNES wrote:
> I'm mostly sending this email because I had an idea, and it's late, and I
> don't
> want to forget.
>
> Today it occured to me that many Test:: extensions are more about better
> diagnostic output than better test comparison.
>
> This stinks:
>
> want: foo bar
> have
I'm mostly sending this email because I had an idea, and it's late, and I don't
want to forget.
Today it occured to me that many Test:: extensions are more about better
diagnostic output than better test comparison.
This stinks:
want: foo bar
have: foo bar
So you write some plugin that doe
