Hi! Again, some more Documentation typos with some fun while we're at it:
1. http://www.sqlite.org/c3ref/intro.html "These pages _defined_ the C-language interface to SQLite." Good old days! 2. http://www.sqlite.org/quickstart.html "... sqlite3_exec() on line _27_ ..." Most C++ editors insist on _28_. 3. http://www.sqlite.org/quickstart.html "... and sqlite3_close() on line _31_ ..." Not to mention _33_. 4. http://www.sqlite.org/cintro.html "The "sqlite3_column()" shown in the list is _place holders_ for an entire _families_ of ..." Further down the page the truth is revealed: "... is really _a place-holder_ for an entire _family_ of ..." 5. http://www.sqlite.org/cintro.html "However, the SQLite allows the same prepared statement _to_ evaluated multiple times." To be, or not _to be_: that is the .. query. 6. http://www.sqlite.org/cintro.html "_These_ is accomplished using the following routines:" Know what? Is hard to make fun of every typo I find. I'm not that resourceful. Couldn't find any jokes for _This_ one. 7. http://www.sqlite.org/cintro.html "SQLite includes _interface_ that can be used to extend its functionality. Such routines include:" The textual construction _faces_ a lack of plural. 8. http://www.sqlite.org/cintro.html "The sqlite3_create_collation() interface is used to create ... The sqlite3_create_module() interface is used __ register ..." It used _to_ be correct in the first sentence but not anymore in the second. .. and the last one, which I hope is taken as a joke and nothing more (by the way, thank you again Mr.Hipp for making easy, even for non-programmers, to use SQL statements from within C++ code): 9. http://www.sqlite.org/cintro.html "A complete list of functions that form the SQLite application _program_ interface ..." Who wrote this definitely doesn't like _programming_ ;) Marian Cascaval _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
