Re: [boost] [compiler workaround] Are we purging history?

Subject: Re: [boost] [compiler workaround] Are we purging history?
From: Nathan Ridge (zeratul976_at_[hidden])
Date: 2013-10-14 02:37:38

> As I understand it, the people modernizing Boost code by getting rid of old compiler workarounds are doing two things:
>
> 1. Remove the workaround macro flags and the code that uses them, leaving the code that doesn't use the workarounds behind.
> 2. Purging those workaround macros from Boost.Config.
>
> If we are doing [2], why? Doing [1] is sufficient for modernization. Doing [2] is just purging history that we spent blood/sweat/tears generating. Authors/maintainers generally have free reign to use as many or as few workarounds as they want. They can't do that if we're deleting that knowledge from Boost.Config.

Boost.Config is also a library whose code people sometimes read
and need to maintain, so the same arguments for removing
unnecessary clutter that justify removing the use of the 
workaround macros in other libraries, I think justify removing 
their definitions from Boost.Config.

The workaround definitions will remain in version control
history, if anyone ever cares about them.

Regards,
Nate