Mercurial > hg > audiodb
view tests/0003/run-test.sh @ 458:913a95f06998 api-inversion
Start using the query state structure.
Actually using it means moving it around in the source code a little
bit, thanks to entanglements. It'll all be alright on the night. Now
the accumulator, allowed_keys and exact_evaluation_queue are all part of
the query state, and can therefore be passed around with minimal effort
(and deleted in the appropriate place).
Now a whole bunch of static methods (the callbacks, basically) in
index.cpp can be rewritten as plain old C functions. The callbacks need
both an adb_t and a query state structure to function (the adb_t to get
at things like lsh_n_point_bits and the track->key table; the qstate to
get at the accumulator and allowed_keys list).
Rearrange audioDB::query a little bit, and mark the beginning and the
end of the putative audiodb_query_spec() API function implementation.
author | mas01cr |
---|---|
date | Sun, 28 Dec 2008 18:44:08 +0000 |
parents | fe4dc39b2dd7 |
children |
line wrap: on
line source
#! /bin/bash . ../test-utils.sh if [ -f testdb ]; then rm -f testdb; fi ${AUDIODB} -d testdb -N # point query now implemented as sequence search ${AUDIODB} -d testdb -L # We could contemplate putting the test feature (and the expected # query output) under svn control if we trust its binary file # handling. # FIXME: endianness! intstring 1 > testfeature floatstring 1 >> testfeature ${AUDIODB} -d testdb -I -f testfeature ${AUDIODB} -d testdb -Q point -f testfeature > test-query-output echo testfeature 1 0 0 > test-expected-query-output cmp test-query-output test-expected-query-output # failure cases expect_clean_error_exit ${AUDIODB} -d testdb -I expect_clean_error_exit ${AUDIODB} -d testdb -f testfeature expect_clean_error_exit ${AUDIODB} -I -f testfeature expect_clean_error_exit ${AUDIODB} -d testdb -Q notpoint -f testfeature expect_clean_error_exit ${AUDIODB} -Q point -f testfeature exit 104