next »

[Daid]

found this: https://github.com/roger-dv/cpp20-coro-generator

seems it's time to start the transition to c++20

Because depending on an experimental feature that is implemented by a single compiler is a good idea?



As for compilers, I hope none of you have to support code that needs to run in both gcc and the armcc compiler. It's a bit of a mess with feature support, especially on C++11 for armcc.

[fluffrabbit]

Why can't you use the GCC cross-compilers?

[nikodil]

seems it's time to start the transition to c++20

Because depending on an experimental feature that is implemented by a single compiler is a good idea?

more like because by the time I've transitioned my custom code that does the same thing (but slower, buggier, and incomplete), it has become standard and supported by all major compilers

and also it's my personal project so I have the luxury of being able to pick and choose the tooling

[Daid]

Why can't you use the GCC cross-compilers?

I can, and I am. But the code is shared along multiple work projects, and some are using the Keil armcc compiler, because that's what they approved for medical projects... (you pay for it, so it must be better right?)

Fun things I found out:
- Compiler crashes if your code uses exceptions and you don't enable them in the compiler flags
- While it states c++11 compatibility, it has to footnote "none of the stl libraries are implemented", even std::initializer_list is missing...
- It happly links in multiple shared libraries containing the same symbols, even if those implementations vastly differ
- It's nested structure initialization parsing is incompatible with gcc. Both support only different syntax.


At least it's not trying to impersonate gcc, like clang is. Which defines __GNUC__, even if it isn't the GNUC compiler. Requiring checks like this: https://github.com/daid/SeriousProton2/blob/master/include/private/collision/box2d.h#L4

[fluffrabbit]

With that mission-critical standardization bureaucracy, I get it. Of course there is no STL. As for the other afflictions, it would seem like 8 years would be long enough to fix things, but what do I know?

Bear in mind Clang is only what it is because GCC went GPLv3 and Steve Jobs had to fix the situation.

[Daid]

Clang also exists because the people behind gcc are bat shit insane. "We shouldn't make the architecture more modular, because that makes it easier to make close source modules, even tough our license does not allow that"

[fluffrabbit]

That explains the spaghetti headers. Without the static linking exception, nobody would use it. But I think Clang uses GCC headers, or a version thereof. I'm not really sure. In any case, there are a lot more decent compiler options when C++ is not a requirement.

[studio28]

I use mostly C++11 at work but like many things(for example coroutines etc) in recent version.