4 ms·
<pedantic>_Generic is not a macro; it just is used a lot inside macros. You should see it as a switch on the type of its argument. This also aren't templates;
by Someone 13y ago
<pedantic>_Generic is not a macro; it just is used a lot inside macros. You should see it as a switch on the type of its argument.
This also aren't templates; you still have to write all those variants for a function, and give them unique names.
More importantly, I think this is worth the hassle. Before this, you couldn't really do
typedef double number_t;
and then easily call functions in the standard library such as sin, acos, or pow without having to worry about the actual type of that typedef. _Generic allows library developers to hide the ugliness of having different names for similar functions. That might have been possible using preprocessor metaprogramming, but it certainly wasn't simple.
- simias 13y agoA fair point, but I think your example demonstrates what I'm worried about: for each legitimate use of this construct there will be a billion of bogus/leaky implementations that we'll have to debug in a couple of years. If I want to write "sin(a);" and let the compiler figure out which implementation of sin to use, I can already do that today. I use C++. It's a bit late to turn C into a strong-ish typed language...
- Someone 13y agoIf you accept "If I want to do X, I can already do that today. I use C++" as an argument, I don't think there is much to be done improving C. You may be able to add a header file here and there before C++ gets it, and you may be able to fix some dark corners of the language, but the big picture would be one of stagnation. Stagnation in programming languages leads to death, so you would accept that C will eventually die, with C++ being its replacement/killer. That is not necessarily a bad thing, and one could argue that it already is happening (are there still self-hosting C compilers?), but I think it is something one should realize the moment one uses that argument.
- Aldo_MX 13y agoMy understanding is that programming languages exist because they attempt to solve an existing problem under a defined paradigm. I'm not against borrowing features from other languages when they can be ported without affecting the paradigm, but when they do... does it mean the language will die without a specific set of features? I believe it's the project manager's responsibility to evaluate whether the problems a project will solve can be solved with a specific language before taking the decision to use it. A language will never be an "all-in-one solution" and forcing a language to solve a problem it was not designed to solve will lead to extra work in the best scenario, ex. String Manipulation in C. My perception about C is that it was the best option available when it emerged, but newer languages emerged that managed to solve specific problems in a better way than C. For me this doesn't mean that C is a "dying language", but the completely opposite, C has become a specialized language suitable for use cases where higher level languages mean "expensive overhead", but lower level languages mean "expensive complexity".