adjusted a statement about InfoObsolete

[ThomasBreuer]

Variables created by DeclareObsoleteSynonym and DeclareObsoleteSynonymAttr
print a message if the InfoObsolete level is high enough.
The current default threshold is 2 for DeclareObsoleteSynonym
and 1 for DeclareObsoleteSynonymAttr,
but the documentation claimed 1 for both.

Perhaps it would be better to change the code to use default 1 (or 2?)
in both cases.

[fingolfin]

I believe the use of two levels was introduced by @ChrisJefferson in PR #2923. So perhaps he'd like to chime in here. Also @alex-konovalov might.

Generally said, I am not sure whether we really want to remove obsolete stuff, ever, unless we have strong reasons for doing so (e.g.: a function requires a certain internal way to represent things in order to work; we want to change those internals, but don't want to put efforts into rewriting an obsolete function for use with the new setup). After all, if there is no immediate gain, why inconvenience our users? We also may want to warn about some obsoletes (without removing them) if their user suggests potentially inefficient or unsafe code, though.

[ThomasBreuer]

O.k., this topic is not relevant enough for more comments. The solution is perhaps not optimal, but it makes the world a little bit better.

[ChrisJefferson]

Just to say, I am happy this was merged, and believe it fixed an earlier mistake of mine. I missed the PR in the pile of emails I received while on holiday. Sorry.

[olexandr-konovalov]

Perhaps it would be better to change the code to use default 1 (or 2?) in both cases.

I think so (if yes, then to 1).