21 ms·
A Perspective on C++ Standardization in 2018
- merlincorey 8y agoA very thorough breakdown of the trials and tribulations of getting things through the C++ Standardization Committee. The article leaves us with the advice that if we care what goes into C++, then, whether we like it or not, we'll need to get involved somehow. This could mean joining things fully, or just communicating your needs to existing members who are aligned with you in some fashion. Sadly, I don't think we'll see much of an uptick in C++ Standards participation in relation to C++ standards complaints.
- deleted 8y ago[deleted]
- Santosh83 8y agoTo what extent is the creator of C++ involved with its Standardization process these days?
- hvs 8y agoHe's the Evolution Working Group Chair. https://isocpp.org/wiki/faq/wg21#bjarne-stroustrup https://isocpp.org/wiki/faq/wg21#bjarne-stroustrup
- johannkokos 8y agoAnd Chair of Direction Group in 2018. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0939r0.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p093...
- bigcheesegs 8y agoHe was previously. The current EWG Chair is Ville Voutilainen.
- lasagnaphil 8y agoThe problem is that C++ is already too much bloated (in its complex rules and the standard library) and some people (primarily gamedev) would want things more to be removed, changed, and simplified rather than continuously added to the pile. But the philosophy of C++ standards development was always about adding new things while maintaining backward compatibility. So even if the gamedev people ask the committee to change its philosophy and remove the bloat, I feel that it would only result in tribal wars between developers and not constructive change. So right now there are two kinds of gamedev: the ones who would suck it up and just use C++ (although not the modern one), or the ones who move to greener pastures. I've heard some gamedev people are moving to Rust (although having the potential to rival C++ in complexity, is nicer because of its fresher base). And Jonathan Blow is currently creating Jai, so maybe that could be a hope of light for gamedev people...
- stinos 8y agoSo right now there are two kinds of gamedev: the ones who would suck it up and just use C++ (although not the modern one) Why can't there be a third kind: the ones who suck it up and just use C++ including modern features? (honest question: I don't know anything at all about 'gamedev')
- lasagnaphil 8y agoUsing modern C++ with STL in gamedev is quite difficult because it results in atrocious compile times and slow debug build performance (For making a game, iteration speed and debuggability can be pretty important.) Also if you want to develop for consoles there are some limitations: most notably you are forbidden to use exceptions, and the platform's compiler usually doesn't even support the latest C++ standard... That said, I think a third kind might also exist, although rare for AAA studios and more common with mid-size/indie game developers...
- Negitivefrags 8y agoThe compiler for Xbox one is MSVC which supports modern c++ quite quickly, and the compiler for PS4 is based on Clang which also supports modern c++ very quickly. Exceptions are supported and we use them for any non-gameplay code paths. That is to say, you can and should use exceptions for all loading/initialisation paths unless they are during actual gameplay. This ends up feeling quite natural as that is mostly what exceptions are good for, and honestly, they would practically never fire in a non-development scenario because they are almost always some kind of error in data files.
- chris_wot 8y agoWhat, precisely, are the warts that folks want to get rid of in C++ but cannot?
- hellofunk 8y agoDepends who you talk to. Here’s one take by the great Scott Meyers: http://scottmeyers.blogspot.com/2015/11/breaking-all-eggs-in-c.html http://scottmeyers.blogspot.com/2015/11/breaking-all-eggs-in...
- slavik81 8y agoJust off the top of my head, it would be nice to remove std::initializer_list from the standard to make uniform initialization truly uniform, and to remove to the 'explicit' keyword to make it the default behaviour. There's also stuff from C that can be surprisingly complicated, like integer promotion rules, but if you change that sort of thing you might as well design a new language from scratch.
- Ace17 8y agoThe preprocessor: Bjarne Stroustrup has been willing to get rid of it for a long time. C++20 modules are a step in this direction. However - as pointed out by John Lakos - you still need macros to build zero-cost logging facilities.
- Ace17 8y agoCorresponding citation from John Lakos about why macros could be necessary: https://www.youtube.com/watch?v=K_fTl_hIEGY&t=3140 https://www.youtube.com/watch?v=K_fTl_hIEGY&t=3140
- frabert 8y agoI don't think that's necessarily true, using constexpr facilities you could make a function do nothing according to a compile-time variable value
- Ace17 8y ago
- otabdeveloper1 8y ago> Use C++98 > Complain it's too simple to be expressive. > Get C++17 > Complain it's too expressive to be simple. Sometimes I think the real goal behind these complaints is not learning anything new or programming anything interesting.
- minipci1321 8y agoWell, one objective part I can see in these complaints, is that it seems to be hard to assemble a sufficiently big team of sufficiently qualified C++ developers, for what the project requires. C++ skills are scarce and expensive. This seems to be confirmed by my own experience in my waters. And then people proceed to put all blame on the language alone, and this does not match the reality anymore. Again, in my waters.
- mschuetz 8y agoOh I absolutely love C++11, 14 and 17. It's just that there are always some really dumb parts that are shipped together with the good parts. Like mandatory begin and end iterators for list comprehension, iota, unreadable syntax of C++20 ranges, etc.