*** 44,50 **** instead of ".c" is that the file is #include-ed into the middle of {link: /cvstrac/rlog?f=sqlite/src/tokenize.c tokenize.c}. The keywordhash.h code file is generated by a custom C program ! named {link /cvstrac/rlog?f=sqlite/tool/mkkeywordhash.c mkkeywordhash.c}. We might have just as easily have hand-coded the keyword hash table, and in fact that was done in earlier versions of SQLite. But the hash table that mkkeywordhash.c is optimized for both --- 44,50 ---- instead of ".c" is that the file is #include-ed into the middle of {link: /cvstrac/rlog?f=sqlite/src/tokenize.c tokenize.c}. The keywordhash.h code file is generated by a custom C program ! named {link: /cvstrac/rlog?f=sqlite/tool/mkkeywordhash.c mkkeywordhash.c}. We might have just as easily have hand-coded the keyword hash table, and in fact that was done in earlier versions of SQLite. But the hash table that mkkeywordhash.c is optimized for both *************** *** 77,85 **** *: *opcodes.h*. This file contains #defines that map opcode names into ! opcode numbers for the Virtual DataBase Engine (VDBE) in the core of SQLite. It is generated by an AWK script that ! uses both the parse.h file generated by Lemon at the {link: /cvstrac/rlog?f=sqlite/src/vdbe.c vdbe.c} source file from CVS as inputs. The vdbe.c file is the implementation of the virtual machine. It is scanned to figure out which --- 77,85 ---- *: *opcodes.h*. This file contains #defines that map opcode names into ! opcode numbers for the Virtual Database Engine (VDBE) in the core of SQLite. It is generated by an AWK script that ! uses both the parse.h file generated by Lemon and the {link: /cvstrac/rlog?f=sqlite/src/vdbe.c vdbe.c} source file from CVS as inputs. The vdbe.c file is the implementation of the virtual machine. It is scanned to figure out which *************** *** 91,97 **** this way makes code generation much easier. *: *opcodes.c*. ! This file makes VDBE opcode numbers back into symbolic names so that symbolic opcode names (rather than obscure opcode numbers) can appear in the output of {link: /lang_explain.html EXPLAIN}. --- 91,97 ---- this way makes code generation much easier. *: *opcodes.c*. ! This file maps VDBE opcode numbers back into symbolic names so that symbolic opcode names (rather than obscure opcode numbers) can appear in the output of {link: /lang_explain.html EXPLAIN}.