1 Nov
2013
1 Nov
'13
7:01 p.m.
John Maddock wrote:
If there are self contained headers in some/many core libraries, then we should use a tool that is smart enough to detect that and behave sensibly. Otherwise move these self-contained details into some sort of "core" module that depends on nothing but config.
That's basically what I suggested as an alternative, some kind of a Utility module that is absolutely not allowed to depend on anything but Config.
How hard is it to create such a library and who would have to buy off on it? It's not like it needs a review given that it's meant for code that's already in boost to be moved into it, just like 'detail' never got a review (I assume).