Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by yencabulator | Hacker News Reader

Parent Full thread

yencabulator·

https://google.github.io/styleguide/cppguide.html

View on HN

Ahh, so just style changes. TY

More than that, the guide limits C++ usage to a safer subset of features.

In addition to style/subset, I also meant using Google's internal standard library.

C++ relies heavily on RAII. Exceptions are safer than broken instances from failed constructors.

In their defense, the style guide says they inherited that from legacy code.

Google C++ doesn't allow using exceptions and therefore requires broken instances from failed constructors.

Google C++ tends towards the convention of constructors that do only cursory initialization to a sane but non-functional state, things that almost-always succeed (and assert on failure), with the "real" initialization pushed to an Init() or Start() function.

Not these days, although that was true 8-9 years ago.

The preferred pattern now is to use factory functions that can return either a fully-initialized object or an error.

Not having exceptions doesn't imply that. An alternative is ErrorOr<ReturnType> returning factory functions. It requires that ReturnType is movable tho (can be further wrapped in std::unique_ptr if not).

Not every error is exceptional so not every error should use exceptions. This is especially important in lower level code where someone's exception is someone else's expected code path.

C++ are many languages in one. It depends which subset you choose.

Reply on news.ycombinator.com