develooper Front page | perl.perl5.porters | Postings from May 2008

Re: TODO Tests

Thread Previous | Thread Next
From:
David Nicol
Date:
May 6, 2008 08:46
Subject:
Re: TODO Tests
Message ID:
934f64a20805060846i30c62401s3974480d48818b3a@mail.gmail.com
On Tue, May 6, 2008 at 2:47 PM, Renée Bäcker
<renee.baecker@smart-websolutions.de>
>
>  Then you have to save what foo() returned when you added the TODO test...
>
>  Renée

My suggestion for how to do this is to check for the existence
${caller().'::WAS'} in
whatever path is currently followed when ${caller().'::TODO'} is set, within the
definition of C<sub is> (or wherever C<local $TODO> is checked, if not there)
and emit an informational notification when the result has changed,
which is AIUI
what Bram wants.

Perhaps C<local $WAS> could be a hashref indexing versions and platforms
to obtained results when the obtained incorrect result is different
different places,
as a way to extend the semantics of $WAS, but initially a scalar holding the
expected wrong result is all that is needed.  Additional hooks might
include text
of the result change notification.



-- 
"For every complex problem, there is a solution that is simple, neat,
and wrong." -- Mencken

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About