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
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
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.
> 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
