glibmm: Glib::ConvertError Class Reference
Exception class for charset conversion errors. More...
#include </home/kjell/checkout/gnome/glibmm-2.4/glib/glibmm/convert.h>
Inheritance diagram for Glib::ConvertError:

Public Types |
Public Member Functions | |
| ConvertError (Code error_code, const Glib::ustring& error_message) | |
| ConvertError (GError* gobject) | |
| Code | code () const |
Public Member Functions inherited from Glib::Error | |
| Error () | |
| Error (GQuark error_domain, int error_code, const Glib::ustring& message) | |
| Error (GError* gobject, bool take_copy=false) | |
| Error (const Error& other) | |
| Error& | operator= (const Error& other) |
| ~Error () noexcept override | |
| GQuark | domain () const |
| int | code () const |
| Glib::ustring | what () const override |
| bool | matches (GQuark error_domain, int error_code) const |
| GError* | gobj () |
| const GError* | gobj () const |
Public Member Functions inherited from Glib::Exception | |
| virtual | ~Exception () noexcept=0 |
Additional Inherited Members | |
Protected Attributes inherited from Glib::Error | |
| GError* | gobject_ |
Detailed Description
Exception class for charset conversion errors.
Glib::convert() and friends throw a ConvertError exception if the charset conversion failed for some reason. When writing non-trivial applications you should always catch those errors, and then try to recover, or tell the user the input was invalid.
Member Enumeration Documentation
Error codes returned by character set conversion routines.
Constructor & Destructor Documentation
| Glib::ConvertError::ConvertError | ( | Code | error_code, |
| const Glib::ustring& | error_message | ||
| ) |
|
explicit |
Member Function Documentation
| Code Glib::ConvertError::code | ( | ) | const |

Public Member Functions inherited from