Author Topic: Modeling C++ exceptions  (Read 275 times)


  • EA User
  • **
  • Posts: 46
  • Karma: +0/-0
    • View Profile
Modeling C++ exceptions
« on: November 09, 2023, 03:21:45 am »
I thought of using Events to model C++ exceptions: an interruptible region (corresponding to C++ try) would have an "unlinked" receive event in it (corresponding to C++ catch) that out-flows into catch-body activities. BUT, events are added as links to a diagram and thus a diagram cannot hold multiple instances of a (same) event. So, different catches cannot be modeled.
I then thought of using Signal, but I cannot really differentiate between "sent"/"received" Signals (thrown/caught).

Do you have an example of how to model C++ exceptions, please?