Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Fix a typo in the assert.html document.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | branch-3.26|
|Files:||files | file ages | folders|
|User & Date:||drh 2018-12-15 11:12:56|
|12:00||Fix typo on the security.html webpage. (check-in: 2ffc105f81 user: drh tags: branch-3.26)|
|11:12||Fix a typo in the assert.html document. (check-in: 538a9a3099 user: drh tags: branch-3.26)|
|02:51||Fix a typo in the code of ethics. (check-in: 6e0f306cb7 user: drh tags: branch-3.26)|
Changes to pages/assert.in.
199 199 running off the end of the linked list in case there is an error in some 200 200 other part of the code that has corrupted the linked list. 201 201 202 202 <p> 203 203 An ALWAYS(X) or NEVER(X) sometimes verifies pre-conditions that are 204 204 subject to change if other parts of the code are modified in 205 205 subtle ways. At [https://sqlite.org/src/artifact/18a53540aa3?ln=5512-5516] 206 -we have a case test for two pre-conditions that are true only because 206 +we have a test for two pre-conditions that are true only because 207 207 of the limited scope of use of the sqlite3BtreeRowCountEst() function. 208 208 Future enhancements to SQLite might use sqlite3BtreeRowCountEst() in 209 209 new ways where those preconditions no longer hold, and the NEVER() 210 210 macros will quickly alert the developers to that fact when the 211 211 situation arises. But if, for some reason, the pre-conditions are 212 212 not satisfied in a release build, the program will still behave sanely 213 213 and will not do an undefined memory access. 214 214 215 215 <p> 216 216 The testcase() macro is often used to verify that boundary 217 217 cases of an inequality comparison are checked. For example, at 218 218 [https://sqlite.org/src/artifact/18a53540aa3?ln=5766]. These 219 219 kind of checks help to prevent off-by-one errors.