diff options
| author | larrybr <larrybr@noemail.net> | 2023-05-13 15:34:15 +0000 |
|---|---|---|
| committer | larrybr <larrybr@noemail.net> | 2023-05-13 15:34:15 +0000 |
| commit | ea51c09a8b835dc32aad85c59dd2e99fb4723ec1 (patch) | |
| tree | bd6b1ab54f4dbdd5b4a7ba203d71a11f7ad26a48 /src | |
| parent | 273c2a9425c04e72c516fa283181b88ce8eb9eb9 (diff) | |
| download | sqlite-ea51c09a8b835dc32aad85c59dd2e99fb4723ec1.tar.gz sqlite-ea51c09a8b835dc32aad85c59dd2e99fb4723ec1.zip | |
Mention that sqlite3_mutex_free() accepts NULL as a no-op.
FossilOrigin-Name: 603d9ad5012ca8996783996d7b8cd6a1aabf12b21604a2ccc137f4c2d99427b9
Diffstat (limited to 'src')
| -rw-r--r-- | src/sqlite.h.in | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/sqlite.h.in b/src/sqlite.h.in index ba7ad9c53..b78adc2a3 100644 --- a/src/sqlite.h.in +++ b/src/sqlite.h.in @@ -7881,7 +7881,7 @@ int sqlite3_vfs_unregister(sqlite3_vfs*); ** ^(Some systems (for example, Windows 95) do not support the operation ** implemented by sqlite3_mutex_try(). On those systems, sqlite3_mutex_try() ** will always return SQLITE_BUSY. The SQLite core only ever uses -** sqlite3_mutex_try() as an optimization so this is acceptable +** sqlite3_mutex_try() as an optimization so this is acceptable ** behavior.)^ ** ** ^The sqlite3_mutex_leave() routine exits a mutex that was @@ -7889,9 +7889,9 @@ int sqlite3_vfs_unregister(sqlite3_vfs*); ** is undefined if the mutex is not currently entered by the ** calling thread or is not currently allocated. ** -** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), or -** sqlite3_mutex_leave() is a NULL pointer, then all three routines -** behave as no-ops. +** ^If the argument to sqlite3_mutex_enter(), sqlite3_mutex_try(), +** sqlite3_mutex_leave(), or sqlite3_mutex_free() is a NULL pointer, +** then any of the four routines behaves as a no-op. ** ** See also: [sqlite3_mutex_held()] and [sqlite3_mutex_notheld()]. */ |