[Dune-devel] Deprecating interfaces type_traits

[Christian Engwer]

> Maybe we should also talk about the duties of deprecating. I know not
> many people really care about removing deprecated functions after the
> next release. But I really dislike when people deprecate a function or
> class, and not adjust affected code. This creates easily dozens of
> warnings which user code cannot avoid.
> I don't want to blame Oliver in particular, it is just the most recent
> example I remember: His deprecation of map() in favor of index() causes
> long lists of deprecation warnings, most of them not in user code but
> VTK output. I'd like to see this changed as part of the deprecation process.
> If the deprecated code is not used anymore, it is less difficult to
> remove it. The only exception should be tests of the deprecated part,
> and it should be enclosed by the DISABLE_DEPRECATED macro.
> Currently it is virtually impossible to use the gridcheck, because there
> are so many warnings about ilevelbegin, leafend etc. -- even with the
> deprecated checks disabled.

I think for test we should disabling the decprecation warnings via the
preprocessor. In these cases we deliberately test the deprecated
feature and thus we don't want to get warning...

Christian