Foobar2000:Development:Exceptions - Revision history

DEATH: Created page with "Category:Foobar2000 Development == Exception use == Most of API functions use C++ exceptions to signal failure conditions. All used exception classes must derive from
2022-06-22T12:20:37Z

Created page with "Category:Foobar2000 Development == Exception use == Most of API functions use C++ exceptions to signal failure conditions. All used exception classes must derive from <co..."

New page
[[Category:Foobar2000 Development]]

== Exception use ==
Most of API functions use C++ exceptions to signal failure conditions. All used exception classes must derive from <code>std::exception</code>; this design allows various instances of code to use single <code>catch()</code> line to obtain human-readable description of the problem to display.

Additionally, special subclasses of exceptions are defined for use in specific conditions, such as <code>exception_io</code> for I/O failures. As a result, you must provide an exception handler whenever you invoke any kind of I/O code that may fail, unless in specific case calling context already handles exceptions (e.g. input implementation code - any exceptions should be forwarded to calling context, since exceptions are a part of input API).

Implementations of global callback services such as <code>playlist_callback</code>, <code>playback_callback</code> or <code>library_callback</code> must not throw unhandled exceptions; behaviors in case they do are undefined (app termination is to be expected).