-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/06/12 08:55, bi...@aol.com wrote: > That's a great suggestion but as I said, my main app is only 400 KB. > I'd really like to keep it that way.
Well, it isn't 400kb if you depend on SQLite being somewhere else on the system. And I find it even stranger that you call this a security app yet somehow depend on a random SQLite somewhere under the control of other apps. > I pride myself in the size and performance of my app. Did you know you can compile SQLite to exclude functionality? http://www.sqlite.org/compile.html#omitfeatures http://www.sqlite.org/footprint.html#relfootprint What I do is have a .c file like this that does all the SQLite interaction: #define SQLITE_API static #include "sqlite3.c" ... my code to access sqlite ... That allows the compiler to do a lot of inlining and making code smaller plus more performant. > I suspect I'm one of the few Windows security apps still using plain C > and a little assembly code. While you can take pride in that sort of thing as a programmer, the reality is that users don't care what language you used, or how hard the code was to write, how it behaves for others, how it works on platforms they don't use etc. What they do care about is if the resulting app works for them and their priorities. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/p+I0ACgkQmOOfHg372QR9/wCeMutBjoaFyFjN/RD6BcdGIovm qLUAnjoCN/z+TByIhefrvqspeqPbWmuV =ROTY -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
