We understand that. Some of us have been - reasonably successfully -
balancing the need for stability/compatibility with the need for
evolution to meet new challenges for decades.

That said, I hope that it is well known that I think that we eventually
have to eliminate macros to get really good tools, and that those really
good tool probably won't be able to handle older code littered with
macros. I'm looking for tools that can help refactor from macros to real
language features.


On 4/11/2018 12:37 PM, Boris Kolpackov wrote:
> Titus Winters <titus_at_[hidden]> writes:
>
>> Yeah, one of the recognized strengths of C++ is that it doesn't leave all
>> of the legacy code behind, generally speaking.
> But there is a cost to this legacy support both in time it takes
> the committee to figure out the battalions of special cases as well
> as the resulting complexity which some of us have no capacity to
> handle and which will most likely limit the "toolability" of the
> end result.
>
> Boris
> _______________________________________________
> Tooling mailing list
> Tooling_at_[hidden]
> http://www.open-std.org/mailman/listinfo/tooling