Hacker News new | ask | show | jobs
by jcelerier 1582 days ago
but this does not make sense. If you can't even change the C++ compiler you use you can't write non-C++ code (e.g. Rust) either.

Otherwise let me just fork Clang into the "Gnalc" compiler for the "Sulpsulpees" language which happens to be exactly compatible with the programming language that the clang++-13 binary supports. Takes me a whole 15 minutes, most of which will be taken by forking the LLVM repo on github, and I can guarantee than porting to it will be less effort than porting to Rust. I can even provide the backing of a proper non-profit foundation established on two continents for your legal team's needs.
1 comments
boondaburrah 1581 days ago
The reason you can't use clang is not a technical one, but that you are /required/ to use the platform's provided C++ compiler.

And yes, you are making my point. We are in violent agreement.

You can't write Rust either, which is why C++ support would be initially exciting, until you learn you can't use just any C++ compiler and the one you can use is excluded.

link
jcelerier 1581 days ago
Who has such stupid requirements ? What's the "platform" compiler for something that provides GCC up to 11, like centos ?
link
boondaburrah 1580 days ago
Embedded stuff usually, game consoles. Also if you have an Enterprise SKU of Visual Studio it costs real money to upgrade. Maybe your company has purchased a compiler suite you have to use. Maybe you have to link against proprietary libs that were only provided for a certain MSVC ABI.
link
jcelerier 1579 days ago
But you originally said: "Yeah the problem isn't nearly as pronounced for rust,"

It does not make sense: the problem is even worse for rust in that case, since you cannot even use it ?

link
boondaburrah 1575 days ago
Exactly, that's why one would get excited for C++ support.

However, I realise the point is moot since there would be no way to compile the library. I've been living too long in "Compiles to C" languages this month I guess.

link