From 07bcb3f8d6451de9d44c1ff5891f7fc79d8fa524 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Thu, 3 Nov 2011 00:05:29 -0400 Subject: [PATCH] Update deprecation docs --- docs/reference/glib/compiling.sgml | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/docs/reference/glib/compiling.sgml b/docs/reference/glib/compiling.sgml index 9d20a58..cc72eda 100644 --- a/docs/reference/glib/compiling.sgml +++ b/docs/reference/glib/compiling.sgml @@ -79,18 +79,22 @@ symbol GLIB_DISABLE_DEPRECATION_WARNINGS by using the commandline option -DGLIB_DISABLE_DEPRECATION_WARNINGS -If you want to make really sure that your program -doesn't use any deprecated functions, you can define the preprocessor -symbol G_DISABLE_DEPRECATED by using the commandline option --DG_DISABLE_DEPRECATED. This will hide deprecated -API from the compiler entirely, most likely causing your program's -build to fail. +The older deprecation mechanism of hiding deprecated interfaces +entirely from the compiler by using the preprocessor symbol +G_DISABLE_DEPRECATED is still used for deprecated macros, +enumeration values, etc. To detect uses of these in your code, +use the commandline option -DG_DISABLE_DEPRECATED. The recommended way of using GLib has always been to only include the toplevel headers glib.h, glib-object.h, gio.h. +Starting with 2.32, GLib enforces this by generating an error +when individual headers are directly included. + + + Still, there are some exceptions; these headers have to be included separately: gmodule.h, @@ -103,11 +107,6 @@ the Internationalization section), (we don't want to pull in all of stdio). - -Starting with 2.32, GLib enforces this by generating an error -when individual headers are directly included. - - -- 2.7.4