database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-07-29 08:01:23 +03:00
Code Activity

Doc typo fixes.

Browse Source 
FossilOrigin-Name: e528675da3971907666c7d2d09763975a105ec585dc5122145f65905d535bed8
This commit is contained in:
stephan
2022-10-02 03:14:38 +00:00
parent 63e9ec2f9c
commit 9fdce595eb
4 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
ext/wasm/api/sqlite3-api-glue.js
View File

@ -276,21 +276,21 @@ self.sqlite3ApiBootstrap.initializers.push(function(sqlite3){
/**
A convenience wrapper for allocChunks() which sizes each chunks
as either 8 bytes (safePtrSize is truthy) or wasm.ptrSizeof (if
safePtrSize is truthy).
safePtrSize is falsy).
How it returns its result differs depending on its first
argument: if it's 1, it returns a single pointer value. If it's
more than 1, it returns the same as allocChunks().
When one of the pointers refers to a 64-bit value, e.g. a
double or int64, and that value must be written or fetch,
When a returned pointers will refer to a 64-bit value, e.g. a
double or int64, and that value must be written or fetched,
e.g. using wasm.setMemValue() or wasm.getMemValue(), it is
important that the pointer in question be aligned to an 8-byte
boundary or else it will not be fetched or written properly and
will corrupt or read neighboring memory.
However, when all pointers involved are "small", it is safe to
pass a falsy value to save to memory.
However, when all pointers involved point to "small" data, it
is safe to pass a falsy value to save to memory.
*/
wasm.pstack.allocPtr = (n=1,safePtrSize=true) =>{
return 1===n

4
ext/wasm/common/whwasmutil.js
View File

@ -1132,8 +1132,8 @@ self.WhWasmUtilInstaller = function(target){
The reason for the 2nd argument is..
When one of the pointers will refer to a 64-bit value, e.g. a
double or int64, an that value must be written or fetch,
When one of the returned pointers will refer to a 64-bit value,
e.g. a double or int64, an that value must be written or fetched,
e.g. using setMemValue() or getMemValue(), it is important that
the pointer in question be aligned to an 8-byte boundary or else
it will not be fetched or written properly and will corrupt or