On 7/17/17, petern <peter.nichvolo...@gmail.com> wrote:
> Missing documentation or wrong extension source?

The documentation and code you are looking are from different branches.

>
> https://www.sqlite.org/src/file/ext/misc/remember.c line 51:
> -> ptr = sqlite3_value_pointer(argv[1], "carray");
>
> This signature, 'void* sqlite3_value_pointer(V,T)' , is not documented here:
>
> https://sqlite.org/draft/c3ref/value_blob.html
>
> Nor is there any mention about the additional parameter T when setting the
> result here:
>
> https://sqlite.org/draft/c3ref/result_blob.html
>
> Nor here:
>
> https://sqlite.org/draft/c3ref/bind_blob.html
>
> I suppose that's consistent but it would be nice to read about the new API.
>
> The only clue about how it works is a brief statement in change header of
> remember.c:
>
> "The pointer type is a string that must compare equal using strcmp() or
> else the pointer comes through as a NULL."
>
> On Thu, Jul 13, 2017 at 11:49 AM, Richard Hipp <d...@sqlite.org> wrote:
>
>> The 3.20.0 release of SQLite is expected in about a week.  Please
>> report any issues that you have with the beta as soon as possible.
>>
>> Code is available in the "prerelease snapshot" at
>> https://sqlite.org/download.html
>>
>> An overview of changes is at https://sqlite.org/draft/
>> releaselog/3_20_0.html
>>
>> You can send issues to this email list, or directly to me.
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> _______________________________________________
>> sqlite-users mailing list
>> sqlite-users@mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>


-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to