3 ms·
If you're doing metaprogramming using the C preprocessor, it's time to move to a more advanced language.
by WalterBright 4y ago
If you're doing metaprogramming using the C preprocessor, it's time to move to a more advanced language.
- FpUser 4y agoI knew someone would come up with this kind of "wisdom". For starters you do not know what other languages they might be using for development. And whatever they do they definitely do not need patronizing.
- WalterBright 4y agoI've done a share of C metaprogramming with the preprocessor myself, and have dealt a lot with other peoples' C metaprogramming. I've also seen people use pages of algrebra as a substitute for a couple lines of calculus. I struggled for years with a soldering iron, always frustrated by bad solder joints. Then, I discovered a Weller thermostat controlled iron, and get a perfect joint every time. Not everyone knows there are better ways to do things.
- webstrand 4y agoYour experience soldering is a much better response. You present a concrete suggestion for use a weller thermostat controlled iron. But you did not present a concrete suggestion for an alternative to the C pre-processor. You could do this with C++ templates, for instance. But the LESS and SWAP operations may or may not get inlined. With the C pre-processor you can be certain that the operations get inlined, since no other alternative interpretation is available to the compiler.
- WalterBright 4y ago> But you did not present a concrete suggestion for an alternative to the C pre-processor. If someone asked, I would. But since I do have a dog in that hunt, I felt it would be more appropriate for others to make a suggestion, as there are several.
- Dalton9 4y agoOh come on, Walter, don't make us beg... Show us how you'd do it in D to achieve the exact same result.
- deleted 4y ago[deleted]
- WalterBright 4y ago> But the LESS and SWAP operations may or may not get inlined. True. But modern inliners are pretty good, and if they can't inline it due to its complexity, it's pretty unlikely it'll be faster. Note the performance comparison in the article. Low level hand-optimizations paid off handsomely in the 1980s, but are usually best left to the compiler's optimizer these days.
- rootw0rm 4y agoSIMD being an exception still (unless maybe Intel compiler + C/C++ + proper annotations)
- alphaglosined 4y agoLLVM can do an awful lot with SIMD that isn't visible in clang. We have experienced this with LDC in D. What I've been told is that LDC produces better IR than clang (I haven't compared, I only know that LDC is practically magical from both mine and other peoples experiments). About the only thing I've seen that has problems with inlining is inline assembly. Intrinsics are fine (which you don't need thanks to vectorization being practically magical as long as you do some annotations like assert and get the memory layout right).
- freedom-fries 4y agoThe article is talking code and demonstrating results. Talk is cheap, show the code!
- ivalm 4y agoParent comment is by the inventor of D, among other things…
- WalterBright 4y agoA rote translation of Q_SORT3 would look like: /* Sort 3 elements. */ void Q_SORT3(alias Q_LESS, alias Q_SWAP, Q_UINT) (Q_UINT q_a1, Q_UINT q_a2, Q_UINT q_a3) { if (Q_LESS(q_a2, q_a1)) { if (Q_LESS(q_a3, q_a2)) Q_SWAP(q_a1, q_a3); else { Q_SWAP(q_a1, q_a2); if (Q_LESS(q_a3, q_a2)) Q_SWAP(q_a2, q_a3); } } else if (Q_LESS(q_a3, q_a2)) { Q_SWAP(q_a2, q_a3); if (Q_LESS(q_a2, q_a1)) Q_SWAP(q_a1, q_a2); } } A D template function is distinguished by having two parameter lists, the compile time parameter list and the runtime parameter list. Q_UINT would be a type parameter with its type inferred from the function arguments. Q_LESS and Q_SWAP are alias parameters, which can be an alias to any symbol or type. This is often used to pass lambdas. Note that D allows the following ways to pass a parameter: 1. by value 2. by reference 3. by name 4. by type The alias parameters are "by name". C++ has by name parameters in the form of template template parameters, along with the restriction that such a parameter can only be a template. D allows any symbol or type to be passed by name. Passing the lambdas by name means a direct function call/inlining rather than an indirect call through a function pointer. Anyhow, with this example you can see how the rest can be fairly easily translated. So, you might ask, what's the advantage? 1. name hygiene 2. your debugger will see the symbols 3. no ugly \ line splicing 4. no wacky do-while(0) kludge 5. the names are actual symbols rather than transitory apparitions seen only by the preprocessor 6. color syntax highlighting in your editor works 7. the compiler will check the syntax and give error messages in terms of the symbols, not generated preprocessor text 8. It's not going to conflict with another symbol named Q_SORT
- FpUser 4y ago>"Not everyone knows there are better ways to do things." In theory you might be right but I doubt it is applicable in this particular case.
- Asooka 4y agoI would probably use a separate templating language to manually generate variants of the function for each type I need, check those in git along with the template.
- taneq 4y agoMaybe they don't want to move to a more advanced language, maybe they want to mess around with the C preprocessor. :)
- WalterBright 4y agoIf you want to show cleverness, by all means! I still use some primitive tools, and know there are better alternatives, but I'm not going to defend sticking with them. BTW, I did win the Obfuscated C contest one year, and (naturally) used the preprocessor: https://www.ioccc.org/1986/bright/bright.c https://www.ioccc.org/1986/bright/bright.c
- rootw0rm 4y agojust last night i was thinking how cool it would be for an IDE plugin that expands rust macros for easier grokking. now i need one for your #defines, lol
- gdprrrr 4y agocargo expand?
- taneq 4y agoMust... resist... being... nerdsniped... oh no too late, now I have to figure out what it's doing without looking it up. :D I've never entered the OCCC but I've read a bunch of past entries and always wanted to enter someday.
- AbsoluteCabbage 4y agoC is still the King of languages.
- WhereIsTheTruth 4y agoI agree with that None of the new languages managed to capture what makes C great The few "modern" ones are interesting, Zig, Jai and Odin for example, I like how they took C designated initialization to the next level Zig's comptime is also nice D is nice, but is loosing its charm now that the competition is here.. also what used to be a D strength now is a weakness; it's slow to compile thanks to the std.. debugging still is a pain, and code can become quite overly verbose
- pjmlp 4y agoAlmost, it is the prince of memory corruption bugs, the throne belongs to Assembly.
- flohofwoe 4y agoIn many cases it's also enough to just enable LTO to give the compiler enough information for stamping out a specialized version. But TBH I'm a bit tired of people shitting on the C preprocessor. It's a relatively simple text replacement tool, and provides an incredible amount of bang for the buck (e.g. many problems can be solved without having to add more specialized bells and whistles to the language). It's a trade-off like anything else in computing.
- jaridivak 4y ago> many problems can be solved without having to invent new language features You mean something like a type checker?
- WalterBright 4y agoThe C preprocessor was an easy and compact way to extend C back when memory was really really tight. You can't even fit a C++98 compiler into DOS's memory space, but you can fit a C compiler in 64K. (Well, an earlier version of C.) C has been adding generics anyway, like _Generic.
- alphaglosined 4y agoAbout a year ago I had a look at a C compiler for 16bit computers, featured in disk form on I think Adrian's digital basement YT channel. The compiler was very basic, nothing like you'd expect from a compiler even from the dragon book. So simple and it was a production compiler too! Sadly I can't remember the name of it to reference here.
- WalterBright 4y agoI wrote one back in 1983 or so for 16 bit DOS, too! A few years later, I was at a C++ conference where they asked me to sit on an "Ask us anything" panel. I was there along with the developers of Microsoft C, Borland C, etc. The first question was "do you still ship a version of your compiler that will run on a floppy disk system?" Vendor 1 said sure, and launched into a long description of how the files could be shuffled about on the floppy to make it work. Vendor 2 said sure, and launched into ... My turn. I said sure, and said the floppy disk version costs $200 and comes with a hard disk drive. (That was the price of a hard disk in those days.) That was the end of that, I never heard that question again from anybody. Progress...
- Y_Y 4y agoYou're right, but also famously an interested party in the promotion of one of these "more advanced languages". People often take bias to mean that a source is false or untrustworthy and I think this is a nice counterexample.
- tpoacher 4y ago"A witty quote proves nothing" ~Voltaire