On 6/19/07, chromatic <[EMAIL PROTECTED]> wrote:
On Tuesday 19 June 2007 14:06:05 Joshua ben Jore wrote:
> It's on CPAN with the original name. I just stole the namespace. I
> don't think chromatic will mind.
>
> It can even support the API described in Perl Hacks if or when it gets
> a custom import/unimport function.
Adding a custom import/unimport or active/deactivate interface should be
doable with a good idea of what people will actually do with it. I'll look
into this.
Here's my use case. At my employer, we're doing some refactoring of
our code and as a close approximation of good coverage took a large
chunk of queries from our logs. If our refactored code still produced
the same thing after our change then that's good. Instead of storing
giant heaping bucketfuls of queries I'd like to store only
non-redundant queries. Since tracing ops is not a perfect oracle to
execution I probably shouldn't store only *one* query per code path
but at least I can choose how much potential redundancy to retain in
my stored queries.
for ( @millions_of_queries ) {
run_search( ... );
if ( not previously_seen_code_path( ... ) ) {
add_to_test_suite( ... );
}
}
Josh
