[llvm-dev] Using C++14 code in LLVM

[via llvm-dev]

>>  It's nice to see this week's version of MSVC supports C++17 but deploying through corporate IT can take a while.

>  But this does apply to LLVM versions, to, doesn't it ? What's the problem with LLVM 9 using c++17 if you can only develop based on LLVM 5 at your shop anyways ?


MSVC must be deployed through corporate IT because it costs money.  Given how widely deployed it is within our organization, I'd expect the incremental cost for my project is minimal, but conversely it means the cost savings of switching build compilers to Clang would be equally minimal.

Clang version N would not have to be deployed through corporate IT, because it doesn't cost money.  But changing the build compiler for our tools in this way would entail a different (and not short) validation process, followed by some amount of infrastructure work to change how my project deploys build tools throughout our automation.  Now, all of that is feasible, but involves person-time not spent directly on improving the actual product delivered to our licensees.  Which management has to be persuaded is a good tradeoff, versus saving the (minimal, see above) dollar cost of the MSVC license.

More than you probably wanted to know, but that's how it works in the various large companies I have worked for.
--paulr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180514/3c66b5c0/attachment.html>