From 4147ff6a4e0fa04d98eba0b27557fa04f63807e3 Mon Sep 17 00:00:00 2001
From: SDL Wiki Bot <[EMAIL REDACTED]>
Date: Sat, 17 Aug 2024 04:39:06 +0000
Subject: [PATCH] Sync SDL3 wiki -> header
---
include/SDL3/SDL_init.h | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/include/SDL3/SDL_init.h b/include/SDL3/SDL_init.h
index c0bd01e30ec75..f942719fad788 100644
--- a/include/SDL3/SDL_init.h
+++ b/include/SDL3/SDL_init.h
@@ -73,13 +73,16 @@ typedef Uint32 SDL_InitFlags;
* https://wiki.libsdl.org/SDL3/README/main-functions#main-callbacks-in-sdl3
* for details.
*
- * Returning SDL_APP_SUCCESS or SDL_APP_FAILURE from SDL_AppInit, SDL_AppEvent, or SDL_AppIterate
- * will terminate the program and report success/failure to the operating system. What that means
- * is platform-dependent. On Unix, for example, on success, the process error code will be zero,
- * and on failure it will be 1. This interface doesn't allow you to return specific exit codes,
- * just whether there was an error generally or not.
- *
- * Returning SDL_APP_CONTINUE from these functions will let the app continue to run.
+ * Returning SDL_APP_SUCCESS or SDL_APP_FAILURE from SDL_AppInit,
+ * SDL_AppEvent, or SDL_AppIterate will terminate the program and report
+ * success/failure to the operating system. What that means is
+ * platform-dependent. On Unix, for example, on success, the process error
+ * code will be zero, and on failure it will be 1. This interface doesn't
+ * allow you to return specific exit codes, just whether there was an error
+ * generally or not.
+ *
+ * Returning SDL_APP_CONTINUE from these functions will let the app continue
+ * to run.
*
* \since This enum is available since SDL 3.0.0.
*/