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_error.h | 226 ----------------------------- 1 file changed, 226 deletions(-) delete mode 100644 contrib/SDL-3.2.8/include/SDL3/SDL_error.h (limited to 'contrib/SDL-3.2.8/include/SDL3/SDL_error.h') diff --git a/contrib/SDL-3.2.8/include/SDL3/SDL_error.h b/contrib/SDL-3.2.8/include/SDL3/SDL_error.h deleted file mode 100644 index 934967c..0000000 --- a/contrib/SDL-3.2.8/include/SDL3/SDL_error.h +++ /dev/null @@ -1,226 +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. -*/ - -/** - * # CategoryError - * - * Simple error message routines for SDL. - * - * Most apps will interface with these APIs in exactly one function: when - * almost any SDL function call reports failure, you can get a human-readable - * string of the problem from SDL_GetError(). - * - * These strings are maintained per-thread, and apps are welcome to set their - * own errors, which is popular when building libraries on top of SDL for - * other apps to consume. These strings are set by calling SDL_SetError(). - * - * A common usage pattern is to have a function that returns true for success - * and false for failure, and do this when something fails: - * - * ```c - * if (something_went_wrong) { - * return SDL_SetError("The thing broke in this specific way: %d", errcode); - * } - * ``` - * - * It's also common to just return `false` in this case if the failing thing - * is known to call SDL_SetError(), so errors simply propagate through. - */ - -#ifndef SDL_error_h_ -#define SDL_error_h_ - -#include - -#include -/* Set up for C function definitions, even when using C++ */ -#ifdef __cplusplus -extern "C" { -#endif - -/* Public functions */ - - -/** - * Set the SDL error message for the current thread. - * - * Calling this function will replace any previous error message that was set. - * - * This function always returns false, since SDL frequently uses false to - * signify a failing result, leading to this idiom: - * - * ```c - * if (error_code) { - * return SDL_SetError("This operation has failed: %d", error_code); - * } - * ``` - * - * \param fmt a printf()-style message format string. - * \param ... additional parameters matching % tokens in the `fmt` string, if - * any. - * \returns false. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_ClearError - * \sa SDL_GetError - * \sa SDL_SetErrorV - */ -extern SDL_DECLSPEC bool SDLCALL SDL_SetError(SDL_PRINTF_FORMAT_STRING const char *fmt, ...) SDL_PRINTF_VARARG_FUNC(1); - -/** - * Set the SDL error message for the current thread. - * - * Calling this function will replace any previous error message that was set. - * - * \param fmt a printf()-style message format string. - * \param ap a variable argument list. - * \returns false. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_ClearError - * \sa SDL_GetError - * \sa SDL_SetError - */ -extern SDL_DECLSPEC bool SDLCALL SDL_SetErrorV(SDL_PRINTF_FORMAT_STRING const char *fmt, va_list ap) SDL_PRINTF_VARARG_FUNCV(1); - -/** - * Set an error indicating that memory allocation failed. - * - * This function does not do any memory allocation. - * - * \returns false. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - */ -extern SDL_DECLSPEC bool SDLCALL SDL_OutOfMemory(void); - -/** - * Retrieve a message about the last error that occurred on the current - * thread. - * - * It is possible for multiple errors to occur before calling SDL_GetError(). - * Only the last error is returned. - * - * The message is only applicable when an SDL function has signaled an error. - * You must check the return values of SDL function calls to determine when to - * appropriately call SDL_GetError(). You should *not* use the results of - * SDL_GetError() to decide if an error has occurred! Sometimes SDL will set - * an error string even when reporting success. - * - * SDL will *not* clear the error string for successful API calls. You *must* - * check return values for failure cases before you can assume the error - * string applies. - * - * Error strings are set per-thread, so an error set in a different thread - * will not interfere with the current thread's operation. - * - * The returned value is a thread-local string which will remain valid until - * the current thread's error string is changed. The caller should make a copy - * if the value is needed after the next SDL API call. - * - * \returns a message with information about the specific error that occurred, - * or an empty string if there hasn't been an error message set since - * the last call to SDL_ClearError(). - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_ClearError - * \sa SDL_SetError - */ -extern SDL_DECLSPEC const char * SDLCALL SDL_GetError(void); - -/** - * Clear any previous error message for this thread. - * - * \returns true. - * - * \threadsafety It is safe to call this function from any thread. - * - * \since This function is available since SDL 3.2.0. - * - * \sa SDL_GetError - * \sa SDL_SetError - */ -extern SDL_DECLSPEC bool SDLCALL SDL_ClearError(void); - -/** - * \name Internal error functions - * - * \internal - * Private error reporting function - used internally. - */ -/* @{ */ - -/** - * A macro to standardize error reporting on unsupported operations. - * - * This simply calls SDL_SetError() with a standardized error string, for - * convenience, consistency, and clarity. - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_Unsupported() SDL_SetError("That operation is not supported") - -/** - * A macro to standardize error reporting on unsupported operations. - * - * This simply calls SDL_SetError() with a standardized error string, for - * convenience, consistency, and clarity. - * - * A common usage pattern inside SDL is this: - * - * ```c - * bool MyFunction(const char *str) { - * if (!str) { - * return SDL_InvalidParamError("str"); // returns false. - * } - * DoSomething(str); - * return true; - * } - * ``` - * - * \threadsafety It is safe to call this macro from any thread. - * - * \since This macro is available since SDL 3.2.0. - */ -#define SDL_InvalidParamError(param) SDL_SetError("Parameter '%s' is invalid", (param)) - -/* @} *//* Internal error functions */ - -/* Ends C function definitions when using C++ */ -#ifdef __cplusplus -} -#endif -#include - -#endif /* SDL_error_h_ */ -- cgit v1.2.3