Below this letter is the diff of my changes, which when used in addition to Matt's, allowed me to use SQLite2 and SQLite3 together (for that test anyway) under Mac OS X 10.2.8.
This change is in the SQLite core, the file "encode.c" to be specific, so someone with commit privileges on sqlite.org will have to apply it.
In summary, I renamed all occurances of sqlite_[encode|decode]_binary() to sqlite3_[encode|decode]_binary() in "encode.c".
FYI, assuming this is accepted into the core (or you can easier redo it yourself with a quick search-n-replace), it will mark the first time I actually ever edited and returned changes to the SQLite core, which to me is special. (And yes, I commit it to the public domain.)
Hopefully this will make it into SQLite 3.0.7, and a corresponding DBD::SQLite 1.06.
-- Darren Duncan
[S0106000393c33758:/Volumes/Programming/DBD-SQLite-1.05] darrenduncan% diff encode.c encode-DARREN.c
107c107
< ** or UPDATE statement. Use sqlite_decode_binary() to convert the
---
> ** or UPDATE statement. Use sqlite3_decode_binary() to convert the
123c123
< int sqlite_encode_binary(const unsigned char *in, int n, unsigned char *out){
---
> int sqlite3_encode_binary(const unsigned char *in, int n, unsigned char *out){
167c167
< ** This routine reverses the encoding created by sqlite_encode_binary().
---
> ** This routine reverses the encoding created by sqlite3_encode_binary().
175c175
< int sqlite_decode_binary(const unsigned char *in, unsigned char *out){
---
> int sqlite3_decode_binary(const unsigned char *in, unsigned char *out){
216c216
< nOut = sqlite_encode_binary(in, n, out);
---
> nOut = sqlite3_encode_binary(in, n, out);
222c222
< if( nOut!=sqlite_encode_binary(in, n, 0) ){
---
> if( nOut!=sqlite3_encode_binary(in, n, 0) ){
238c238
< j = sqlite_decode_binary(out, out);
---
> j = sqlite3_decode_binary(out, out);
