Move C++98 support to a branch named 'legacy'

[DBJDBJ]

No description provided.

[martinmoene]

How would you explain the issue?

[DBJDBJ]

Hi Martin, well probably like this:

It is not feasible to go bellow C++ version that is more than 8 years old. For good people in a real "need" for C++98, let them congregate around (and fork from) the "legacy" branch.
I hope onlookers do realise C++17 and C++98 are two different languages.

Important to notice: the suggested branch is not to be called "deprecated" it is to be called "legacy". Contributors who need this version are welcome to contribute.

Something along these lines?

[Quuxplusone]

@DBJDBJ: I believe Martin's question is, why should this be done? It sounds like (A) you've asked for some work to be done in the repo; (B) you've just now given a reasonable explanation as to why this work would not be very harmful to most users; but you haven't given any thought to (C) whether this work would be helpful to anybody.

[DBJDBJ]

@Quuxplusone ... feasibility Arthur :) Ie the amount of effort to make something that is useful and already exists in C++11 onwards or (god forbid, only) in the standard C++ onwards. So this work (which I have not specifically asked for) would be helpful to the maintainers of the project. First.