From 30f41c02aec763d32e62351452da9ef582bc3472 Mon Sep 17 00:00:00 2001 From: 3gg <3gg@shellblade.net> Date: Fri, 6 Mar 2026 13:30:59 -0800 Subject: Move contrib libraries to contrib repo --- contrib/SDL-3.2.8/include/SDL3/SDL_assert.h | 662 ---------------------------- 1 file changed, 662 deletions(-) delete mode 100644 contrib/SDL-3.2.8/include/SDL3/SDL_assert.h (limited to 'contrib/SDL-3.2.8/include/SDL3/SDL_assert.h') diff --git a/contrib/SDL-3.2.8/include/SDL3/SDL_assert.h b/contrib/SDL-3.2.8/include/SDL3/SDL_assert.h deleted file mode 100644 index 6c90acc..0000000 --- a/contrib/SDL-3.2.8/include/SDL3/SDL_assert.h +++ /dev/null @@ -1,662 +0,0 @@ -/* - Simple DirectMedia Layer - Copyright (C) 1997-2025 Sam Lantinga - - This software is provided 'as-is', without any express or implied - warranty. In no event will the authors be held liable for any damages - arising from the use of this software. - - Permission is granted to anyone to use this software for any purpose, - including commercial applications, and to alter it and redistribute it - freely, subject to the following restrictions: - - 1. The origin of this software must not be misrepresented; you must not - claim that you wrote the original software. If you use this software - in a product, an acknowledgment in the product documentation would be - appreciated but is not required. - 2. Altered source versions must be plainly marked as such, and must not be - misrepresented as being the original software. - 3. This notice may not be removed or altered from any source distribution. -*/ - -/** - * # CategoryAssert - * - * A helpful assertion macro! - * - * SDL assertions operate like your usual `assert` macro, but with some added - * features: - * - * - It uses a trick with the `sizeof` operator, so disabled assertions - * vaporize out of the compiled code, but variables only referenced in the - * assertion won't trigger compiler warnings about being unused. - * - It is safe to use with a dangling-else: `if (x) SDL_assert(y); else - * do_something();` - * - It works the same everywhere, instead of counting on various platforms' - * compiler and C runtime to behave. - * - It provides multiple levels of assertion (SDL_assert, SDL_assert_release, - * SDL_assert_paranoid) instead of a single all-or-nothing option. - * - It offers a variety of responses when an assertion fails (retry, trigger - * the debugger, abort the program, ignore the failure once, ignore it for - * the rest of the program's run). - * - It tries to show the user a dialog by default, if possible, but the app - * can provide a callback to handle assertion failures however they like. - * - It lets failed assertions be retried. Perhaps you had a network failure - * and just want to retry the test after plugging your network cable back - * in? You can. - * - It lets the user ignore an assertion failure, if there's a harmless - * problem that one can continue past. - * - It lets the user mark an assertion as ignored for the rest of the - * program's run; if there's a harmless problem that keeps popping up. - * - It provides statistics and data on all failed assertions to the app. - * - It allows the default assertion handler to be controlled with environment - * variables, in case an automated script needs to control it. - * - It can be used as an aid to Clang's static analysis; it will treat SDL - * assertions as universally true (under the assumption that you are serious - * about the asserted claims and that your debug builds will detect when - * these claims were wrong). This can help the analyzer avoid false - * positives. - * - * To use it: compile a debug build and just sprinkle around tests to check - * your code! - */ - -#ifndef SDL_assert_h_ -#define SDL_assert_h_ - -#include - -#include -/* Set up for C function definitions, even when using C++ */ -#ifdef __cplusplus -extern "C" { -#endif - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * The level of assertion aggressiveness. - * - * This value changes depending on compiler options and other preprocessor - * defines. - * - * It is currently one of the following values, but future SDL releases might - * add more: - * - * - 0: All SDL assertion macros are disabled. - * - 1: Release settings: SDL_assert disabled, SDL_assert_release enabled. - * - 2: Debug settings: SDL_assert and SDL_assert_release enabled. - * - 3: Paranoid settings: All SDL assertion macros enabled, including - * SDL_assert_paranoid. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_ASSERT_LEVEL SomeNumberBasedOnVariousFactors - -#elif !defined(SDL_ASSERT_LEVEL) -#ifdef SDL_DEFAULT_ASSERT_LEVEL -#define SDL_ASSERT_LEVEL SDL_DEFAULT_ASSERT_LEVEL -#elif defined(_DEBUG) || defined(DEBUG) || \ - (defined(__GNUC__) && !defined(__OPTIMIZE__)) -#define SDL_ASSERT_LEVEL 2 -#else -#define SDL_ASSERT_LEVEL 1 -#endif -#endif - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * Attempt to tell an attached debugger to pause. - * - * This allows an app to programmatically halt ("break") the debugger as if it - * had hit a breakpoint, allowing the developer to examine program state, etc. - * - * This is a macro--not a function--so that the debugger breaks on the source - * code line that used SDL_TriggerBreakpoint and not in some random guts of - * SDL. SDL_assert uses this macro for the same reason. - * - * If the program is not running under a debugger, SDL_TriggerBreakpoint will - * likely terminate the app, possibly without warning. If the current platform - * isn't supported, this macro is left undefined. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_TriggerBreakpoint() TriggerABreakpointInAPlatformSpecificManner - -#elif defined(_MSC_VER) && _MSC_VER >= 1310 - /* Don't include intrin.h here because it contains C++ code */ - extern void __cdecl __debugbreak(void); - #define SDL_TriggerBreakpoint() __debugbreak() -#elif defined(_MSC_VER) && defined(_M_IX86) - #define SDL_TriggerBreakpoint() { _asm { int 0x03 } } -#elif defined(ANDROID) - #include - #define SDL_TriggerBreakpoint() assert(0) -#elif SDL_HAS_BUILTIN(__builtin_debugtrap) - #define SDL_TriggerBreakpoint() __builtin_debugtrap() -#elif SDL_HAS_BUILTIN(__builtin_trap) - #define SDL_TriggerBreakpoint() __builtin_trap() -#elif (defined(__GNUC__) || defined(__clang__)) && (defined(__i386__) || defined(__x86_64__)) - #define SDL_TriggerBreakpoint() __asm__ __volatile__ ( "int $3\n\t" ) -#elif (defined(__GNUC__) || defined(__clang__)) && defined(__riscv) - #define SDL_TriggerBreakpoint() __asm__ __volatile__ ( "ebreak\n\t" ) -#elif ( defined(SDL_PLATFORM_APPLE) && (defined(__arm64__) || defined(__aarch64__)) ) /* this might work on other ARM targets, but this is a known quantity... */ - #define SDL_TriggerBreakpoint() __asm__ __volatile__ ( "brk #22\n\t" ) -#elif defined(SDL_PLATFORM_APPLE) && defined(__arm__) - #define SDL_TriggerBreakpoint() __asm__ __volatile__ ( "bkpt #22\n\t" ) -#elif defined(_WIN32) && ((defined(__GNUC__) || defined(__clang__)) && (defined(__arm64__) || defined(__aarch64__)) ) - #define SDL_TriggerBreakpoint() __asm__ __volatile__ ( "brk #0xF000\n\t" ) -#elif defined(__GNUC__) || defined(__clang__) - #define SDL_TriggerBreakpoint() __builtin_trap() /* older gcc may not support SDL_HAS_BUILTIN(__builtin_trap) above */ -#elif defined(__386__) && defined(__WATCOMC__) - #define SDL_TriggerBreakpoint() { _asm { int 0x03 } } -#elif defined(HAVE_SIGNAL_H) && !defined(__WATCOMC__) - #include - #define SDL_TriggerBreakpoint() raise(SIGTRAP) -#else - /* SDL_TriggerBreakpoint is intentionally left undefined on unknown platforms. */ -#endif - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * A macro that reports the current function being compiled. - * - * If SDL can't figure how the compiler reports this, it will use "???". - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_FUNCTION __FUNCTION__ - -#elif defined(__STDC_VERSION__) && (__STDC_VERSION__ >= 199901L) /* C99 supports __func__ as a standard. */ -# define SDL_FUNCTION __func__ -#elif ((defined(__GNUC__) && (__GNUC__ >= 2)) || defined(_MSC_VER) || defined (__WATCOMC__)) -# define SDL_FUNCTION __FUNCTION__ -#else -# define SDL_FUNCTION "???" -#endif - -/** - * A macro that reports the current file being compiled. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_FILE __FILE__ - -/** - * A macro that reports the current line number of the file being compiled. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_LINE __LINE__ - -/* -sizeof (x) makes the compiler still parse the expression even without -assertions enabled, so the code is always checked at compile time, but -doesn't actually generate code for it, so there are no side effects or -expensive checks at run time, just the constant size of what x WOULD be, -which presumably gets optimized out as unused. -This also solves the problem of... - - int somevalue = blah(); - SDL_assert(somevalue == 1); - -...which would cause compiles to complain that somevalue is unused if we -disable assertions. -*/ - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * A macro for wrapping code in `do {} while (0);` without compiler warnings. - * - * Visual Studio with really aggressive warnings enabled needs this to avoid - * compiler complaints. - * - * the `do {} while (0);` trick is useful for wrapping code in a macro that - * may or may not be a single statement, to avoid various C language - * accidents. - * - * To use: - * - * ```c - * do { SomethingOnce(); } while (SDL_NULL_WHILE_LOOP_CONDITION (0)); - * ``` - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_NULL_WHILE_LOOP_CONDITION (0) - -#elif defined(_MSC_VER) /* Avoid /W4 warnings. */ -/* "while (0,0)" fools Microsoft's compiler's /W4 warning level into thinking - this condition isn't constant. And looks like an owl's face! */ -#define SDL_NULL_WHILE_LOOP_CONDITION (0,0) -#else -#define SDL_NULL_WHILE_LOOP_CONDITION (0) -#endif - -/** - * The macro used when an assertion is disabled. - * - * This isn't for direct use by apps, but this is the code that is inserted - * when an SDL_assert is disabled (perhaps in a release build). - * - * The code does nothing, but wraps `condition` in a sizeof operator, which - * generates no code and has no side effects, but avoid compiler warnings - * about unused variables. - * - * \param condition the condition to assert (but not actually run here). - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_disabled_assert(condition) \ - do { (void) sizeof ((condition)); } while (SDL_NULL_WHILE_LOOP_CONDITION) - -/** - * Possible outcomes from a triggered assertion. - * - * When an enabled assertion triggers, it may call the assertion handler - * (possibly one provided by the app via SDL_SetAssertionHandler), which will - * return one of these values, possibly after asking the user. - * - * Then SDL will respond based on this outcome (loop around to retry the - * condition, try to break in a debugger, kill the program, or ignore the - * problem). - * - * \since This enum is available since SDL 3.2.0. - */ -typedef enum SDL_AssertState -{ - SDL_ASSERTION_RETRY, /**< Retry the assert immediately. */ - SDL_ASSERTION_BREAK, /**< Make the debugger trigger a breakpoint. */ - SDL_ASSERTION_ABORT, /**< Terminate the program. */ - SDL_ASSERTION_IGNORE, /**< Ignore the assert. */ - SDL_ASSERTION_ALWAYS_IGNORE /**< Ignore the assert from now on. */ -} SDL_AssertState; - -/** - * Information about an assertion failure. - * - * This structure is filled in with information about a triggered assertion, - * used by the assertion handler, then added to the assertion report. This is - * returned as a linked list from SDL_GetAssertionReport(). - * - * \since This struct is available since SDL 3.2.0. - */ -typedef struct SDL_AssertData -{ - bool always_ignore; /**< true if app should always continue when assertion is triggered. */ - unsigned int trigger_count; /**< Number of times this assertion has been triggered. */ - const char *condition; /**< A string of this assert's test code. */ - const char *filename; /**< The source file where this assert lives. */ - int linenum; /**< The line in `filename` where this assert lives. */ - const char *function; /**< The name of the function where this assert lives. */ - const struct SDL_AssertData *next; /**< next item in the linked list. */ -} SDL_AssertData; - -/** - * Never call this directly. - * - * Use the SDL_assert macros instead. - * - * \param data assert data structure. - * \param func function name. - * \param file file name. - * \param line line number. - * \returns assert state. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - */ -extern SDL_DECLSPEC SDL_AssertState SDLCALL SDL_ReportAssertion(SDL_AssertData *data, - const char *func, - const char *file, int line) SDL_ANALYZER_NORETURN; - - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * The macro used when an assertion triggers a breakpoint. - * - * This isn't for direct use by apps; use SDL_assert or SDL_TriggerBreakpoint - * instead. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_AssertBreakpoint() SDL_TriggerBreakpoint() - -#elif !defined(SDL_AssertBreakpoint) -# if defined(ANDROID) && defined(assert) - /* Define this as empty in case assert() is defined as SDL_assert */ -# define SDL_AssertBreakpoint() -# else -# define SDL_AssertBreakpoint() SDL_TriggerBreakpoint() -# endif -#endif /* !SDL_AssertBreakpoint */ - -/** - * The macro used when an assertion is enabled. - * - * This isn't for direct use by apps, but this is the code that is inserted - * when an SDL_assert is enabled. - * - * The `do {} while(0)` avoids dangling else problems: - * - * ```c - * if (x) SDL_assert(y); else blah(); - * ``` - * - * ... without the do/while, the "else" could attach to this macro's "if". We - * try to handle just the minimum we need here in a macro...the loop, the - * static vars, and break points. The heavy lifting is handled in - * SDL_ReportAssertion(). - * - * \param condition the condition to assert. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_enabled_assert(condition) \ - do { \ - while ( !(condition) ) { \ - static struct SDL_AssertData sdl_assert_data = { 0, 0, #condition, 0, 0, 0, 0 }; \ - const SDL_AssertState sdl_assert_state = SDL_ReportAssertion(&sdl_assert_data, SDL_FUNCTION, SDL_FILE, SDL_LINE); \ - if (sdl_assert_state == SDL_ASSERTION_RETRY) { \ - continue; /* go again. */ \ - } else if (sdl_assert_state == SDL_ASSERTION_BREAK) { \ - SDL_AssertBreakpoint(); \ - } \ - break; /* not retrying. */ \ - } \ - } while (SDL_NULL_WHILE_LOOP_CONDITION) - -#ifdef SDL_WIKI_DOCUMENTATION_SECTION - -/** - * An assertion test that is normally performed only in debug builds. - * - * This macro is enabled when the SDL_ASSERT_LEVEL is >= 2, otherwise it is - * disabled. This is meant to only do these tests in debug builds, so they can - * tend to be more expensive, and they are meant to bring everything to a halt - * when they fail, with the programmer there to assess the problem. - * - * In short: you can sprinkle these around liberally and assume they will - * evaporate out of the build when building for end-users. - * - * When assertions are disabled, this wraps `condition` in a `sizeof` - * operator, which means any function calls and side effects will not run, but - * the compiler will not complain about any otherwise-unused variables that - * are only referenced in the assertion. - * - * One can set the environment variable "SDL_ASSERT" to one of several strings - * ("abort", "break", "retry", "ignore", "always_ignore") to force a default - * behavior, which may be desirable for automation purposes. If your platform - * requires GUI interfaces to happen on the main thread but you're debugging - * an assertion in a background thread, it might be desirable to set this to - * "break" so that your debugger takes control as soon as assert is triggered, - * instead of risking a bad UI interaction (deadlock, etc) in the application. - * - * \param condition boolean value to test. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_assert(condition) if (assertion_enabled && (condition)) { trigger_assertion; } - -/** - * An assertion test that is performed even in release builds. - * - * This macro is enabled when the SDL_ASSERT_LEVEL is >= 1, otherwise it is - * disabled. This is meant to be for tests that are cheap to make and - * extremely unlikely to fail; generally it is frowned upon to have an - * assertion failure in a release build, so these assertions generally need to - * be of more than life-and-death importance if there's a chance they might - * trigger. You should almost always consider handling these cases more - * gracefully than an assert allows. - * - * When assertions are disabled, this wraps `condition` in a `sizeof` - * operator, which means any function calls and side effects will not run, but - * the compiler will not complain about any otherwise-unused variables that - * are only referenced in the assertion. - * - * One can set the environment variable "SDL_ASSERT" to one of several strings - * ("abort", "break", "retry", "ignore", "always_ignore") to force a default - * behavior, which may be desirable for automation purposes. If your platform - * requires GUI interfaces to happen on the main thread but you're debugging - * an assertion in a background thread, it might be desirable to set this to - * "break" so that your debugger takes control as soon as assert is triggered, - * instead of risking a bad UI interaction (deadlock, etc) in the application. - * * - * - * \param condition boolean value to test. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_assert_release(condition) SDL_disabled_assert(condition) - -/** - * An assertion test that is performed only when built with paranoid settings. - * - * This macro is enabled when the SDL_ASSERT_LEVEL is >= 3, otherwise it is - * disabled. This is a higher level than both release and debug, so these - * tests are meant to be expensive and only run when specifically looking for - * extremely unexpected failure cases in a special build. - * - * When assertions are disabled, this wraps `condition` in a `sizeof` - * operator, which means any function calls and side effects will not run, but - * the compiler will not complain about any otherwise-unused variables that - * are only referenced in the assertion. - * - * One can set the environment variable "SDL_ASSERT" to one of several strings - * ("abort", "break", "retry", "ignore", "always_ignore") to force a default - * behavior, which may be desirable for automation purposes. If your platform - * requires GUI interfaces to happen on the main thread but you're debugging - * an assertion in a background thread, it might be desirable to set this to - * "break" so that your debugger takes control as soon as assert is triggered, - * instead of risking a bad UI interaction (deadlock, etc) in the application. - * - * \param condition boolean value to test. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_assert_paranoid(condition) SDL_disabled_assert(condition) - -/* Enable various levels of assertions. */ -#elif SDL_ASSERT_LEVEL == 0 /* assertions disabled */ -# define SDL_assert(condition) SDL_disabled_assert(condition) -# define SDL_assert_release(condition) SDL_disabled_assert(condition) -# define SDL_assert_paranoid(condition) SDL_disabled_assert(condition) -#elif SDL_ASSERT_LEVEL == 1 /* release settings. */ -# define SDL_assert(condition) SDL_disabled_assert(condition) -# define SDL_assert_release(condition) SDL_enabled_assert(condition) -# define SDL_assert_paranoid(condition) SDL_disabled_assert(condition) -#elif SDL_ASSERT_LEVEL == 2 /* debug settings. */ -# define SDL_assert(condition) SDL_enabled_assert(condition) -# define SDL_assert_release(condition) SDL_enabled_assert(condition) -# define SDL_assert_paranoid(condition) SDL_disabled_assert(condition) -#elif SDL_ASSERT_LEVEL == 3 /* paranoid settings. */ -# define SDL_assert(condition) SDL_enabled_assert(condition) -# define SDL_assert_release(condition) SDL_enabled_assert(condition) -# define SDL_assert_paranoid(condition) SDL_enabled_assert(condition) -#else -# error Unknown assertion level. -#endif - -/** - * An assertion test that is always performed. - * - * This macro is always enabled no matter what SDL_ASSERT_LEVEL is set to. You - * almost never want to use this, as it could trigger on an end-user's system, - * crashing your program. - * - * One can set the environment variable "SDL_ASSERT" to one of several strings - * ("abort", "break", "retry", "ignore", "always_ignore") to force a default - * behavior, which may be desirable for automation purposes. If your platform - * requires GUI interfaces to happen on the main thread but you're debugging - * an assertion in a background thread, it might be desirable to set this to - * "break" so that your debugger takes control as soon as assert is triggered, - * instead of risking a bad UI interaction (deadlock, etc) in the application. - * - * \param condition boolean value to test. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_assert_always(condition) SDL_enabled_assert(condition) - - -/** - * A callback that fires when an SDL assertion fails. - * - * \param data a pointer to the SDL_AssertData structure corresponding to the - * current assertion. - * \param userdata what was passed as `userdata` to SDL_SetAssertionHandler(). - * \returns an SDL_AssertState value indicating how to handle the failure. - * - * \threadsafety This callback may be called from any thread that triggers an - * assert at any time. - * - * \since This datatype is available since SDL 3.2.0. - */ -typedef SDL_AssertState (SDLCALL *SDL_AssertionHandler)( - const SDL_AssertData *data, void *userdata); - -/** - * Set an application-defined assertion handler. - * - * This function allows an application to show its own assertion UI and/or - * force the response to an assertion failure. If the application doesn't - * provide this, SDL will try to do the right thing, popping up a - * system-specific GUI dialog, and probably minimizing any fullscreen windows. - * - * This callback may fire from any thread, but it runs wrapped in a mutex, so - * it will only fire from one thread at a time. - * - * This callback is NOT reset to SDL's internal handler upon SDL_Quit()! - * - * \param handler the SDL_AssertionHandler function to call when an assertion - * fails or NULL for the default handler. - * \param userdata a pointer that is passed to `handler`. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_GetAssertionHandler - */ -extern SDL_DECLSPEC void SDLCALL SDL_SetAssertionHandler( - SDL_AssertionHandler handler, - void *userdata); - -/** - * Get the default assertion handler. - * - * This returns the function pointer that is called by default when an - * assertion is triggered. This is an internal function provided by SDL, that - * is used for assertions when SDL_SetAssertionHandler() hasn't been used to - * provide a different function. - * - * \returns the default SDL_AssertionHandler that is called when an assert - * triggers. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_GetAssertionHandler - */ -extern SDL_DECLSPEC SDL_AssertionHandler SDLCALL SDL_GetDefaultAssertionHandler(void); - -/** - * Get the current assertion handler. - * - * This returns the function pointer that is called when an assertion is - * triggered. This is either the value last passed to - * SDL_SetAssertionHandler(), or if no application-specified function is set, - * is equivalent to calling SDL_GetDefaultAssertionHandler(). - * - * The parameter `puserdata` is a pointer to a void*, which will store the - * "userdata" pointer that was passed to SDL_SetAssertionHandler(). This value - * will always be NULL for the default handler. If you don't care about this - * data, it is safe to pass a NULL pointer to this function to ignore it. - * - * \param puserdata pointer which is filled with the "userdata" pointer that - * was passed to SDL_SetAssertionHandler(). - * \returns the SDL_AssertionHandler that is called when an assert triggers. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_SetAssertionHandler - */ -extern SDL_DECLSPEC SDL_AssertionHandler SDLCALL SDL_GetAssertionHandler(void **puserdata); - -/** - * Get a list of all assertion failures. - * - * This function gets all assertions triggered since the last call to - * SDL_ResetAssertionReport(), or the start of the program. - * - * The proper way to examine this data looks something like this: - * - * ```c - * const SDL_AssertData *item = SDL_GetAssertionReport(); - * while (item) { - * printf("'%s', %s (%s:%d), triggered %u times, always ignore: %s.\\n", - * item->condition, item->function, item->filename, - * item->linenum, item->trigger_count, - * item->always_ignore ? "yes" : "no"); - * item = item->next; - * } - * ``` - * - * \returns a list of all failed assertions or NULL if the list is empty. This - * memory should not be modified or freed by the application. This - * pointer remains valid until the next call to SDL_Quit() or - * SDL_ResetAssertionReport(). - * - * \threadsafety This function is not thread safe. Other threads calling - * SDL_ResetAssertionReport() simultaneously, may render the - * returned pointer invalid. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_ResetAssertionReport - */ -extern SDL_DECLSPEC const SDL_AssertData * SDLCALL SDL_GetAssertionReport(void); - -/** - * Clear the list of all assertion failures. - * - * This function will clear the list of all assertions triggered up to that - * point. Immediately following this call, SDL_GetAssertionReport will return - * no items. In addition, any previously-triggered assertions will be reset to - * a trigger_count of zero, and their always_ignore state will be false. - * - * \threadsafety This function is not thread safe. Other threads triggering an - * assertion, or simultaneously calling this function may cause - * memory leaks or crashes. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_GetAssertionReport - */ -extern SDL_DECLSPEC void SDLCALL SDL_ResetAssertionReport(void); - -/* Ends C function definitions when using C++ */ -#ifdef __cplusplus -} -#endif -#include - -#endif /* SDL_assert_h_ */ -- cgit v1.2.3