Add `DUNE_NO_DEPRECATED_BEGIN` and `DUNE_NO_DEPRECATED_END` macros

These macros can be used to mark a block in which deprecation warnings are ignored. This can be useful for implementations of deprecated methods that call other deprecated methods or for testing deprecated methods in the testsuite.

See also the discussion in dune-grid!61 (merged)

mentioned in merge request dune-grid!61 (merged)

Added 1 commit:

• 36f12fce - Add DUNE_NO_DEPRECATED_START and DUNE_NO_DEPRECATED_END macros

Added 1 commit:

• 565abf9f - Add DUNE_NO_DEPRECATED_START and DUNE_NO_DEPRECATED_END macros

In theory it might be good enough to just implement the __GCC__ case: both icc and clang define that macro and seem to understand gcc's diagnostic pragmas (I had the __GCC__ case first originally and it worked on all three compilers).

Nice, back before 2.4 I had something like this hand-coded around all of the isParallel blocks...

Good to see a more sane and complete solution!

Reassigned to @smuething

Milestone changed to DUNE 3.0.0

If nobody shouts out any major complaints, I'll merge this after the weekend.

Cool. What are the compiler constraints? Are all Dune-3.0-required compilers compatible?

@gruenich The _Pragma operator is C++11 (and C99). Unknown pragma directives must be ignored by the compiler (though I think they result in warnings) [16.6 in my C++11 draft].

So in the worst case, the compiler will still emit deprecation warnings, but the program will still work.

Added 1 commit:

• f1826045 - Add DUNE_NO_DEPRECATED_BEGIN and DUNE_NO_DEPRECATED_END macros

One minor change: I renamed the DUNE_NO_DEPRECATED_START macro to DUNE_NO_DEPRECATED_BEGIN as that seems to be slightly more suggestive (reminding of begin and end in Pascal-derived languages).

Title changed from Add DUNE_NO_DEPRECATED_START and DUNE_NO_DEPRECATED_END macros to Add DUNE_NO_DEPRECATED_BEGIN and DUNE_NO_DEPRECATED_END macros

mentioned in commit a3947bae

Status changed to merged

Mentioned in commit a3947bae