public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sqlite3: deprecated declarations
Date: Fri, 21 Apr 2017 11:51:00 -0000	[thread overview]
Message-ID: <da652f67-a3c5-4989-427e-6eaecddb5aa2@cygwin.com> (raw)
In-Reply-To: <CAO1jNwv1f5VJzqFuNaT3GR73as-XuyqDWx_yA3679LgUA9a2bA@mail.gmail.com>

On 2016-09-02 04:12, Jan Nijtmans wrote:
> 2016-09-02 8:23 GMT+02:00 Yaakov Selkowitz:
>> Please enable deprecated declarations in sqlite3.h.  While it's nice in
>> theory to say that they are deprecated and shouldn't be used, the reality is
>> that real-world code still uses them and therefore fails to build as-is
>> without them.
>
> Thanks!  I'll do that in the next build.

Ping?  This is still an issue with 3.16.2-1.

> Still, I'm interested to know
> which real-word code still uses it, so a bug-report can be sent
> to them. All of those 6 functions where deprecated for a reason!
>
> SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*);

PHP's pdo_sqlite uses this.

> SQLITE_DEPRECATED int sqlite3_expired(sqlite3_stmt*);

qt*-webkit and webkitgtk use this.

> SQLITE_DEPRECATED int sqlite3_transfer_bindings(sqlite3_stmt*, sqlite3_stmt*);

Python's sqlite3 extension uses this.

> SQLITE_DEPRECATED int sqlite3_global_recover(void);
> SQLITE_DEPRECATED void sqlite3_thread_cleanup(void);
> SQLITE_DEPRECATED int sqlite3_memory_alarm(void(*)(void*,sqlite3_int64,int),
>                       void*,sqlite3_int64);

I'm not aware of anything using these.

-- 
Yaakov

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-04-21  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  6:24 Yaakov Selkowitz
2016-09-02  9:12 ` Jan Nijtmans
2017-04-21 11:51   ` Yaakov Selkowitz [this message]
2017-04-25 17:52     ` Jan Nijtmans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da652f67-a3c5-4989-427e-6eaecddb5aa2@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).