"Shane Harrelson" <[EMAIL PROTECTED]> wrote: > > This allowed me to get the benefits of the single source file (more compiler > optimizations, etc.) while keeping the manageability, etc. of the separate > source file. >
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. I know that for my own projects, the use of the amalgamation has greatly simplified configuration management. Now I have just two files (sqlite3.[ch]) that I drop into my project and I'm done. Before I had to either create an external dependency on a external SQLite library and manage that, or import 60+ code files in to a subdirectory with its own makefile, etc. What a pain. Chris Peachment points out that his "Pelles C" compiler (never heard of that one before, but presumably it has its purposes) is unable to compile sqlite3.c, presumably because the file is is too large. This is the only reason I have heard yet for wanting to use separate source file that makes any sense to me. Can somebody please explain to my how 2 files is less manageable than 60? -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
