On 17 November 2016 at 03:58, lhmouse wrote:
> If a program is compiled with `-fno-exceptions` and an exception
> will have been thrown otherwise, `std::abort()` (or an equivalent such as
> `__builtin_trap()`) is called. This preserves the semantical correctness
> of not checking the value of a thr
> GCC is built with -fno-exceptions. I assume that's mainly to avoid
> having to catch and handle exceptions in what was originally C code.
> I also assume that also means that there's a policy or convention in
> place against throwing exceptions in GCC or making use of constructs
> that might thr
On 11/16/2016 07:36 PM, Segher Boessenkool wrote:
On Wed, Nov 16, 2016 at 01:48:41PM -0700, Martin Sebor wrote:
I'm also curious if there really is a policy/convention for dealing
with exceptions in GCC, what it actually is/says.
https://gcc.gnu.org/codingconventions.html#Exceptions
Thanks.
On Wed, Nov 16, 2016 at 01:48:41PM -0700, Martin Sebor wrote:
> I'm also curious if there really is a policy/convention for dealing
> with exceptions in GCC, what it actually is/says.
https://gcc.gnu.org/codingconventions.html#Exceptions
Segher
GCC is built with -fno-exceptions. I assume that's mainly to avoid
having to catch and handle exceptions in what was originally C code.
I also assume that also means that there's a policy or convention in
place against throwing exceptions in GCC or making use of constructs
that might throw (such
