Documentation Source Text

Check-in [2f0174e967]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix typo in the pointer-passing document.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 2f0174e96763d8b5a1aa5fe2ed9737650efc92a9b320a926114ebad1b75e1e5a
User & Date: drh 2017-07-25 15:40:05.513
Context
2017-07-25
15:57
More typo fixes. (check-in: 9fdf1274f9 user: drh tags: trunk)
15:40
Fix typo in the pointer-passing document. (check-in: 2f0174e967 user: drh tags: trunk)
2017-07-24
15:29
Further typo fixes in the pointer-passing document. (check-in: 3ae0a793ec user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/bindptr.in.
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
why they were introduced, and what problem they solve.  This essay attempts
to answer those questions and clear up the confusion.

<h1>A Brief History Of Pointer Passing In SQLite</h1>

<p>
It is sometimes convenient for SQLite extensions to
communicatin non-SQL values between subcomponents or between the extension
and the application.  Some examples:

<ul>
<li><p>
In the [FTS3] extension, the 
[FTS MATCH|MATCH operator] (which does the full-text search)
needs to communicate details of matching entrys to the [snippet()], [offsets()],







|







19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
why they were introduced, and what problem they solve.  This essay attempts
to answer those questions and clear up the confusion.

<h1>A Brief History Of Pointer Passing In SQLite</h1>

<p>
It is sometimes convenient for SQLite extensions to
communicate non-SQL values between subcomponents or between the extension
and the application.  Some examples:

<ul>
<li><p>
In the [FTS3] extension, the 
[FTS MATCH|MATCH operator] (which does the full-text search)
needs to communicate details of matching entrys to the [snippet()], [offsets()],