On Sun, Jan 22, 2012 at 8:29 AM, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:
On 01/22/2012 12:00 PM, Vicente J. Botet Escriba wrote:
I recognize that it could be difficult for libraries as Boost.Thread or Boost.FileSystem, but I don't think Boost.System will be on this case as its dependency are really minor, isn't it? Could you explain more deeply the problem you want to avoid?
error_code.cpp includes windows.h and puts lots of symbol in the global namespace.
Right. Including windows.h is a non-starter in a header. error_code.cpp also makes extensive use of the unnamed namespace. That's also something that isn't normally permissible in a header.
I'm not sure #include "local_free_on_destruction.hpp" works either in a scenario where the file is included.
Good question. I'm not sure either.
So there are problems with the approach of including .cpp files as-is, and a better approach must be found.
Exactly! --Beman