Sorry for being pedantic and possibly ruining the joke: SBRM is actually a subset of RAII because it only applies to automatic variables (hence "scope bound").
In C++ they're alternative tokens and should be keywords, so maybe googletest is providing them as macros as workaround for a compile that didn't support this?
In other words, maybe a computer flag would allow you to disable them being defined?
Yeah I kind of thought it was something like that, but searching for such broad terms got me nowhere, and the googletest documentation wasn't good enough for me to find it.
Only reason I can think of is that conditional breakpoints in the debugger can be much slower than compiling that same condition right into the debuggee.
The only reason is that many still don't learn how to use debuggers, people write blog posts about language featuritis, rewrite X in Y, and then keep using debuggers as if stuck in the 1960's.
grandparent is not advocating making it unconditional, but just adding the nop instruction to the __asm part.
Inserting an unconditional debug trap into a shipping, production executable, is a complete nonstarter. The program will receive a signal that is fatal, if unhandled.
Hmm... interesting. Spain should be covered by GDPR so you should be able to say "I reject right to process my personal data" and it should stop...
I had issue with Vodafone here - they were pestering me with calls/messages... even after I switched to Digi they were calling me for a week to try to convince me to stay (it just confirmed my decission to switch ;) )
I self learned to type using "Iankey"[0] (the manual[1]). In my opinion, it is one of the best training tools I tried - I should search around my old backups to see if I can still find it.
The "fully charged show" sometimes have videos on this and similar topics. This [0] video goes through the pros and cons of using hydrogen in different ways
My takeaway is that as much of the energy as possible should be used without converting it. This avoids the substantial losses converting to and from hydrogen. But storage is one of the viable uses.
SE/SE is called out explicitly in the ISO26262 documents (functional safety in road vehicles). This makes it easy to defend the inclusion of such a guideline, even if you may not agree with it.
But as it happens, MISRA C++:2023 doesn't have this guideline.
Definitely a generalisation, but i would see them as two sides of the same coin.
If Cert has something about an API, then it will have an example of misuse of it and then an example showing its correct use.
MISRA might either prohibit it's use completely (if there's a safe alternative), or with require some boilerplate step be taken every time the API is used.
*Scoped bound resource management... which I had to look up because I never remember it!