News for hackers. Stuff that matters.
Re:Misra C++:2023 Published by lelanthran on Sunday December 17, 2023 @02:29PM (#38675607)
For what definition of "easy"?

Simply passing by value can result in a constructor that fails, while still bypassing any of the factory functions.

Re:Misra C++:2023 Published by jupp0r on Sunday December 17, 2023 @03:45PM (#38676226)
Easy as in "competent C++ programmers do this every day"?

If the copy constructor can fail and you don't want that, then delete it?

Re:Misra C++:2023 Published by lelanthran on Monday December 18, 2023 @08:47AM (#38682380)
> If the copy constructor can fail and you don't want that, then delete it?

You're trivialising just how deeply embedded exceptions are into the design of the language.

I gave just one example and it was not meant to be exhaustive, just one 'gotcha' that you won't find out till runtime and your program starts (worst case) giving you slightly incorrect results without you knowing about it...

So, yeah, if you want to do without exceptions (without having your program execute random code) you need to know in advance what special cases to handle, like unintended copy construction, or failures in overloaded operators, or which std libs can be used and which cannot, or which C++ libraries can be linked, and which cannot.

All of which is perfectly possible, but taken together is hardly "easy". It's tedious, error-prone, bloated ... but hardly what someone would call "easy".

Re:Misra C++:2023 Published by jupp0r on Monday December 18, 2023 @09:17AM (#38682831)
C++ is complicated, I get it. Things that are "easy" in other languages are "hard" in C++. That doesn't mean that writing C++ code that can't throw isn't something that tens of thousands of engineers are doing every day. One could argue that all of C++ is tedious, bloated and error-prone.
Re:Misra C++:2023 Published by kwant_kiddo on Sunday December 17, 2023 @04:01PM (#38676375)
it is easy? It is the named constructor idiom.

I don't understand why jupp0r is getting downvoted?

Most big public c++ projects turn off exceptions, so it seems to be the norm more than anything.

Re:Misra C++:2023 Published by gpderetta on Sunday December 17, 2023 @04:22PM (#38676585)
Because two phase construction is a widely disliked idiom. Named constructors retuning optional objects are tolerable though.
Re:Misra C++:2023 Published by jupp0r on Sunday December 17, 2023 @05:27PM (#38677094)
Two phase construction isn't widely disliked, it's completely fine if it's used as an implementation detail of a factory.
Re:Misra C++:2023 Published by pjmlp on Monday December 18, 2023 @01:49AM (#38679892)
Only the big public C++ projects that blindly follow Google's style guide, mostly.
Re:Misra C++:2023 Published by kwant_kiddo on Monday December 18, 2023 @06:02AM (#38681120)
I don't think this is true, but I don't know this for sure. From what I have read it seems that 'only' Bloomberg, Meta and Microsoft that uses c++ with exceptions.

And since both microsoft and meta are adopting rust in their services it seems to me that they are looking for another language than C++. (why else adopt a new language?)

Following seems not to use exceptions(?)

LLVM: https://llvm.org/docs/CodingStandards.html#do-not-use-rtti-o...

AWS: (seems to be using Google's guidelines to be fair)

Webkit: https://gist.github.com/derofim/df604f2bf65a506223464e3ffd96...

Qt: https://doc.qt.io/qt-6/exceptionsafety.html

gcc: https://gcc.gnu.org/codingconventions.html#Exceptions

Unreal: (not totally sure, but I think it uses error codes internally)

Most of the embedded world. + any console game you ever played or heard of.

Re:Misra C++:2023 Published by pjmlp on Monday December 18, 2023 @08:02AM (#38681838)
LLVM has been for quite some time driven by Apple and Google.

WebKit, another Apple child.

Qt, it has to support environments where exceptions are not allowed, otherwise they would be losing customers, specially since Qt is older than C++98.

gcc, was initially written in C, and for quite long time had a mixed code base with minimal C++.

The companies adopting Rust aren't doing so because of lack of exceptions, they would still adopt Rust if the language had exceptions support (which panic and std::ops::Try kind of are), rather due to the type safety that C and C++ aren't able to provide.

You would be surprised how many games actually do support exceptions.