Back to Basics: Exceptions Klaus Iglberger, CppCon 2020 klaus.iglberger@gmx.de2 Klaus Iglberger C++ Trainer since 2016 Author of the C++ math library (Co-)Organizer of the Munich deContent 3 The Exception Situation How Do Exceptions Work Best Practices of Exception Handling When to Use Exceptions (And When Not) How to Use Exceptions The Exception Safety Guarantees How to Write CodeContent 4 The Exception Situation How Do Exceptions Work Best Practices of Exception Handling When to Use Exceptions (And When Not) How to Use Exceptions The Exception Safety Guarantees How to Write

EXCEPTIONS UNDER THE SPOTLIGHT INBAL LEVIWHO AM I? • AC++ enthusiast. • An embedded software engineer at Solar Edge working on smart home. • One of the organizers of CoreCpp conference and user group founders of the Israeli NB. • I’ve studied physics, I also love math.  2MOTIVATION Q14 Is throwing exceptions to report errors allowed throughout your current project? ISO Survey 2020 45.1% 37.1% 17.8% Audio 54.9% 3 How many of you are using Exceptions in your projects?• Many industries and C++ projects (Such as Embedded, GPUs and Gaming) avoid using exceptions for performance reasons. • The error

C++ Exceptions for Smaller Firmware By: Khalil Estell (@kammce)@kammce Graduated 2017 from SJSU Ex-Googler (~6y) Volunteer @ SJSU ISO C++ Committee Member 2Motivation 345Microcontroller Constraints: into C++26 @ St Louis 2024 ISO C++ meetingTIME SPACE So why do firmware developers avoid C++ exceptions? 14 Requires Dynamic Memory/Heap Increases Binary Size Requires whole C++ STL Run Time Type me / 2); p_pin.level(false); delay(p_transition_time / 2); } 31 The code if we used exceptions…32 The code if we used std::expected status toggle_led( output_pin& p_pin, milliseconds p_transition_time

2023 Bloomberg Finance L.P. All rights reserved. Exceptionally Bad: The story on the misuse of exceptions and how to do better Core C++ June 7, 2023 Pete Muldoon Senior Engineering Lead© 2023 Bloomberg Exceptionally Bad: The story on the misuse of exceptions and how to do better Core C++ June 7, 2023 Pete Muldoon Senior Engineering Lead Exceptions in C++ Better Design Through Analysis of Real World going ? • Talk will be about Exceptions as seen in C++ • Look at original goals/ideals of exception handling • Look at the mechanics of throw/catch • Look at Exceptions in both their use and design as

for Flask Larger Applications Application Factories Application Dispatching Implementing API Exceptions Using URL Processors Deploying with Setuptools Deploying with Fabric Using SQLite 3 with Flask KeyError [https://docs.python.org/3/library/exceptions.html#KeyError] is raised. You can catch it like a standard KeyError [https://docs.python.org/3/library/exceptions.html#KeyError] but if you don’t do that accessing URL parameters with get or by catching the KeyError [https://docs.python.org/3/library/exceptions.html#KeyError] because users might change the URL and presenting them a 400 bad request page in

retry after 1 minute raise self.retry(exc=exc, countdown=60) Automatic retry for known exceptions New in version 4.0. Sometimes you just want to retry a task whenever a particular exception is automatically retry a task using autoretry_for argument in the task() decorator: from twitter.exceptions import FailWhaleError @app.task(autoretry_for=(FailWhaleError,)) def refresh_timeline(user): return twitter.refresh_timeline(user) This is provided as an alternative to manually handling the exceptions, and the example above will do the same as wrapping the task body in a try [https://docs.python

retry after 1 minute raise self.retry(exc=exc, countdown=60) Automatic retry for known exceptions New in version 4.0. Sometimes you just want to retry a task whenever a particular exception is automatically retry a task using autoretry_for argument in the task() decorator: from twitter.exceptions import FailWhaleError @app.task(autoretry_for=(FailWhaleError,)) def refresh_timeline(user): return twitter.refresh_timeline(user) This is provided as an alternative to manually handling the exceptions, and the example above will do the same as wrapping the task body in a try [https://docs.python

retry after 1 minute raise self.retry(exc=exc, countdown=60) Automatic retry for known exceptions New in version 4.0. Sometimes you just want to retry a task whenever a particular exception is automatically retry a task using autoretry_for argument in the task() decorator: from twitter.exceptions import FailWhaleError @app.task(autoretry_for=(FailWhaleError,)) def refresh_timeline(user): return twitter.refresh_timeline(user) This is provided as an alternative to manually handling the exceptions, and the example above will do the same as wrapping the task body in a try [https://docs.python

retry after 1 minute raise self.retry(exc=exc, countdown=60) Automatic retry for known exceptions New in version 4.0. Sometimes you just want to retry a task whenever a particular exception is automatically retry a task using autoretry_for argument in the task() decorator: from twitter.exceptions import FailWhaleError @app.task(autoretry_for=(FailWhaleError,)) def refresh_timeline(user): return twitter.refresh_timeline(user) This is provided as an alternative to manually handling the exceptions, and the example above will do the same as wrapping the task body in a try [https://docs.python

retry after 1 minute raise self.retry(exc=exc, countdown=60) Automatic retry for known exceptions New in version 4.0. Sometimes you just want to retry a task whenever a particular exception is automatically retry a task using autoretry_for argument in the task() decorator: from twitter.exceptions import FailWhaleError @app.task(autoretry_for=(FailWhaleError,)) def refresh_timeline(user): return twitter.refresh_timeline(user) This is provided as an alternative to manually handling the exceptions, and the example above will do the same as wrapping the task body in a try [https://docs.python