drh wrote: > I'm still having trouble trying to understand how managing > 60 separate code files is perceived to be easier than managing > just 2 files (sqlite3.c and sqlite3.h). It seems to me that > the management problem gets much easier the fewer files there > are to manage.
In the case someone wants to use SQLite unchanged, it is certainly easier to manage only 2 files than 60+. But there are people - like myself - who would appreciate to have a source distribution containing the preprocessed source files as separate files as it was before. Not instead of the amalgamation distribution, but additionally. I don't know why others want or need the separate files, but I certainly can explain why I do: I have written an extension for SQLite using C++ which needs the preprocessed header files for compiling. Additionally I have to change the SQLite code at one place (essentially adding a single function call in the pager). The code change is not a big problem, but extracting the header files is quite inconvenient. Unfortunately I can't avoid to extract the header files since I can't merge my own code with SQLite code due to the fact, that SQLite is written in C and my extension in C++, and SQLite is not compilable in C++ mode. So, I would be grateful if the separate file distribution would return in addition to the amalgamation distribution. Regards, Ulrich Telle ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
