add flatbuffers support and initial rewrite
Signed-off-by: Folling <mail@folling.io>
This commit is contained in:
parent
7e883d24eb
commit
98cb7a44ef
72 changed files with 3929 additions and 1403 deletions
|
|
@ -4,11 +4,10 @@
|
|||
/// \author Folling <folling@ikarus.world>
|
||||
|
||||
#include <ikarus/macros.h>
|
||||
#include <ikarus/stdtypes.h>
|
||||
|
||||
/// \addtogroup errors Errors
|
||||
/// \brief Error handling within libikarus
|
||||
/// \details Functions in Ikarus may fail, in which case they have an out parameter for the error.
|
||||
/// \details Functions in Ikarus may fail. To report the type of failure all functions have an out parameter for the error.
|
||||
/// Upon erring the function will store relevant information about the error in the out parameter.
|
||||
/// If the out parameter is null nothing will be stored. This is not recommended as it essentially ignores errors.
|
||||
/// For the sake of simplicity we have avoided mechanisms that "force" clients to handle errors.
|
||||
|
|
@ -93,7 +92,7 @@ enum IkarusErrorInfo {
|
|||
};
|
||||
|
||||
/// \brief The maximum length of an error message.
|
||||
size_t const IKARUS_ERROR_DATA_MAX_MESSAGE_LIMIT = 128;
|
||||
#define IKARUS_ERROR_DATA_MAX_MESSAGE_LIMIT 128
|
||||
|
||||
/// \brief The data stored for an error
|
||||
struct IkarusErrorData {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue