Home/ Questions/Q 6187775
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T02:06:58+00:00

I thought exceptions imposed a bit more on the thrown type than the standard

  • 0

I thought exceptions imposed a bit more on the thrown type than the standard actually imposes. I want to clear up this confusion. What is actually imposed on those types?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The C++ ISO spec, §15.1/3, states that

    The type of the throw-expression shall not be an
    incomplete type, or a pointer or reference to an incomplete type, other than void*, const void*, volatile void*, or const volatile void*. Except for these restrictions and the restrictions on type matching mentioned in 15.3, the operand of throw is treated exactly as a function argument in a call (5.2.2) or the operand of a return statement.

    From this, it seems that you should be able to throw anything you’d like, as long as you’re not throwing a type that you’ve only forward-declared.

    EDIT: As @Billy ONeal points out, the type must be copyable, which means that it should support a copy constructor.

    • 0