[gtk+/wip/ricotz/deprecated: 3/4] gdk: Remove deprecated gdk_threads_set_lock_functions

[Rico Tzschichholz <ricotz src gnome org>]

commit b19fe8f4e0e186f70397c5e86e935df54cc3df46
Author: Rico Tzschichholz <ricotz ubuntu com>
Date:   Mon Oct 24 10:26:03 2016 +0200

    gdk: Remove deprecated gdk_threads_set_lock_functions

 docs/reference/gdk/gdk4-sections.txt |    1 -
 gdk/gdk.c                            |   43 ----------------------------------
 gdk/gdkthreads.h                     |    3 --
 3 files changed, 0 insertions(+), 47 deletions(-)
---
diff --git a/docs/reference/gdk/gdk4-sections.txt b/docs/reference/gdk/gdk4-sections.txt
index 59808a0..10629d0 100644
--- a/docs/reference/gdk/gdk4-sections.txt
+++ b/docs/reference/gdk/gdk4-sections.txt
@@ -633,7 +633,6 @@ GDK_THREADS_LEAVE
 gdk_threads_init
 gdk_threads_enter
 gdk_threads_leave
-gdk_threads_set_lock_functions
 gdk_threads_add_idle
 gdk_threads_add_idle_full
 gdk_threads_add_timeout
diff --git a/gdk/gdk.c b/gdk/gdk.c
index e7e1b3c..46cd9c5 100644
--- a/gdk/gdk.c
+++ b/gdk/gdk.c
@@ -670,49 +670,6 @@ gdk_threads_init (void)
     gdk_threads_unlock = gdk_threads_impl_unlock;
 }
 
-/**
- * gdk_threads_set_lock_functions: (skip)
- * @enter_fn:   function called to guard GDK
- * @leave_fn: function called to release the guard
- *
- * Allows the application to replace the standard method that
- * GDK uses to protect its data structures. Normally, GDK
- * creates a single #GMutex that is locked by gdk_threads_enter(),
- * and released by gdk_threads_leave(); using this function an
- * application provides, instead, a function @enter_fn that is
- * called by gdk_threads_enter() and a function @leave_fn that is
- * called by gdk_threads_leave().
- *
- * The functions must provide at least same locking functionality
- * as the default implementation, but can also do extra application
- * specific processing.
- *
- * As an example, consider an application that has its own recursive
- * lock that when held, holds the GTK+ lock as well. When GTK+ unlocks
- * the GTK+ lock when entering a recursive main loop, the application
- * must temporarily release its lock as well.
- *
- * Most threaded GTK+ apps won’t need to use this method.
- *
- * This method must be called before gdk_threads_init(), and cannot
- * be called multiple times.
- *
- * Deprecated:3.6: All GDK and GTK+ calls should be made from the main
- *     thread
- *
- * Since: 2.4
- **/
-void
-gdk_threads_set_lock_functions (GCallback enter_fn,
-                                GCallback leave_fn)
-{
-  g_return_if_fail (gdk_threads_lock == NULL &&
-                    gdk_threads_unlock == NULL);
-
-  gdk_threads_lock = enter_fn;
-  gdk_threads_unlock = leave_fn;
-}
-
 static gboolean
 gdk_threads_dispatch (gpointer data)
 {
diff --git a/gdk/gdkthreads.h b/gdk/gdkthreads.h
index 8bdc3e4..7d4a9a9 100644
--- a/gdk/gdkthreads.h
+++ b/gdk/gdkthreads.h
@@ -46,9 +46,6 @@ GDK_THREADS_DEPRECATED
 void     gdk_threads_enter                    (void);
 GDK_THREADS_DEPRECATED
 void     gdk_threads_leave                    (void);
-GDK_THREADS_DEPRECATED
-void     gdk_threads_set_lock_functions       (GCallback enter_fn,
-                                               GCallback leave_fn);
 
 GDK_AVAILABLE_IN_ALL
 guint    gdk_threads_add_idle_full            (gint           priority,