On Sat, Mar 14, 2009 at 04:15:46PM +0100, Andreas Altergott wrote:
> This test case has nothing to do with the benchmark suite, does it?
That's right. It's just a smaller task, and directly applicable to ongoing
discussions between Nate, Mike, and I on this list.
> If it doesn't then why is it preferable to write it in Perl?
It might not be. :)
Either would be fine.
> Later on we'll have to port it to C anyway.
Within trunk/perl/t in the KinoSearch repository, you'll see the following.
* A trunk/perl/t/core/ directory, with about 30 test files in it. These
are done; the .t files are just stubs.
* A trunk/perl/t/binding directory, with a handful of files in it. These
are also done; their purpose is to test the Perl binding.
* About 100 test files in t/ itself. These files need to migrate to either
t/core or t/binding.
I was thinking that this would be a "binding" test, but you're right --
pluggable deletions need to be tested in core. We might also write tests to
verify that the binding works (and doesn't leak memory, etc), but that's more
superficial.
Marvin Humphrey
