Programming Books

Let's get an actual thread going.

Post your favourite computer science, mathematics, and programming textbooks.

I'll start with a few that aren't posted all that much.

- The Elements of Computing Systems
Shows the implementation of basically everything, from stringing together logic gates all the way to a compiler, OS, VM, interpreter, etc.

- Types and Programming Languages + Advanced Topics in Types and Programming Languages
A good abstract treatise of type systems and programming language theory.

- Lisp in Small Pieces
Basically an entire book about the implementation of Scheme and Lisp interpreters and compilers.

- Artificial Intelligence: A Systems Approach
A good practical overview of most AI algorithms, covers search, NNs, unsupervised & probabilistic algorithms, genetic and evolutionary algorithms, etc. Example code in C.

>>167,170
Here is a nice table:
CREATE TABLE LIBRARY
(
HASH_ID unsigned smallint(32767),
TITLE nvarchar(128),
AUTHOR nvarchar(64),
TOPIC nvarchar(128),
CATEGORIES ntext(16384),
MEDIA_TYPE nvarchar(128),
FILE longblob(536870912),
FILE_TYPE nvarchar(32),
COMMENTS ntext(16384),
NOTES ntext(16384),
FILE_HASH long(4096),
DATE_CHECKED_IN datetime(4,'localtime'),
DATE_MODIFIED datetime(now,'localtime'),
);
Notes:
HASH_ID is the hash table ID, for easy parsing, than the rest of the table. It can be a GUID if you like. I just use numeric hashes, but they can be strings.
FILE_HASH is the file's hash value, like in sha256 or MD5. You pick your hash value.
FILE is optional.
DATE_CHECKED_IN is the check in date, when the file was first entered into the database.

You should make another table for the hash value of the entries in the table themselves, to validate corruption. Make another for the entries' hash table, and append the global databases hash values.

Caveats:
locatime in SQLite needs fixing before the year 2037. OpenBSD base is already under way.