On 1 Nov 2013 at 14:13, Beman Dawes wrote:
IMO that is the best way to handle this. No point in Boosters putting in effort to work around a problem so serious it blocks most use of clang on windows anyhow. They will have to fix it if they are serious about clang and windows.
Last time I looked clang could generate reasonably functional Win32 EH tables on 32 bit x86. x64 uses a different format, and wasn't working last time I looked. Just because clang can spit out the tables doesn't of course mean that clang's runtime can cope fully yet. Certain support library code would be needed, and I have no idea what the state of that is. I absolutely agree there is no point even thinking about Boost support for clang on Windows as if it were MSVC until they have MSVC native exception handling perfected and Win32 SEH as well, as that comes with the territory of full MSVC compliance. I'd also not bother until clang can fully grok all Win32 Platform SDK headers too, as Boost code will assume that works ifdef _MSC_VER and rightly so. Niall -- Currently unemployed and looking for work. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/