From 85366343968e93bcafa77900d640ae3ebde7fb9a Mon Sep 17 00:00:00 2001 From: Jeff Trull Date: Tue, 30 Jun 2020 12:24:00 -0700 Subject: [PATCH] Deprecate C++03 and re-deprecate the old preprocessor hooks (#104) Targeting a one year transition period for C++03 -> C++11 and one release less to finally get off the old hooks - assuming there are even any users of them. Also added documentation per @pdimov recommendations at https://pdimov.github.io/articles/phasing_out_cxx03.html#_suggested_policy --- ChangeLog | 1 + doc/class_ref_ctxpolicy_depr.html | 2 +- doc/compiletime_config.html | 2 ++ include/boost/wave/wave_config.hpp | 15 +++++++++++++++ 4 files changed, 19 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 6730bce..766cf32 100644 --- a/ChangeLog +++ b/ChangeLog @@ -24,6 +24,7 @@ Boost V1.74: - Repaired two samples and added a new one for macro naming enforcement - Implemented C++20 changes for variadic macros, including __VA_OPT__() - Added C++17 feature __has_include() + - Deprecate C++98 and C++03. Support will end with 1.77. Boost V1.73: - Fixed TRAC #7822: waveidl sample does not use the IDL lexer diff --git a/doc/class_ref_ctxpolicy_depr.html b/doc/class_ref_ctxpolicy_depr.html index e8df187..92da7d2 100644 --- a/doc/class_ref_ctxpolicy_depr.html +++ b/doc/class_ref_ctxpolicy_depr.html @@ -32,7 +32,7 @@

Introduction

Please note that the following description relates to a depreciated interface as it was used by default up to Boost V1.34.x. For the new interface please refer to The Context Policy. You can still force to use this older interface by defining the BOOST_WAVE_USE_DEPRECIATED_PREPROCESSING_HOOKS preprocessing constant as outlined in the Compile -Time Configuration section. By default the new interface is used starting Boost V1.35.0, while the older one is used by default otherwise.

+Time Configuration section. By default the new interface is used starting Boost V1.35.0, while the older one is used by default otherwise. The old interface will be removed entirely with Boost 1.76.

The context policy is used to provide callback hooks, which are called from inside the library into the user code, whenever