Mercurial > sdl-ios-xcode
view docs/man3/SDL_Quit.3 @ 3095:75483112b97f
Date: Sat, 21 Mar 2009 19:41:52 -0700 (PDT)
From: Mason Wheeler
Subject: [SDL] Critical SDL 1.3 patch
Displaying a window created with SDL_CreateWindowFrom was causing stack overf
lows for me under certain conditions. After far too much work trying to get
Visual Studio's debugger to play nice with a program written in Delphi, I tra
cked it down to a nasty reentrancy cycle in the WndProc handling. Here's a p
atch that fixes the problem
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Mon, 23 Mar 2009 02:02:30 +0000 |
| parents | 546f7c1eb755 |
| children | 1238da4a7112 |
line wrap: on
line source
.TH "SDL_Quit" "3" "Tue 11 Sep 2001, 23:00" "SDL" "SDL API Reference" .SH "NAME" SDL_Quit \- Shut down SDL .SH "SYNOPSIS" .PP \fB#include "SDL\&.h" .sp \fBvoid \fBSDL_Quit\fP\fR(\fBvoid\fR); .SH "DESCRIPTION" .PP \fBSDL_Quit\fP shuts down all SDL subsystems and frees the resources allocated to them\&. This should always be called before you exit\&. For the sake of simplicity you can set \fBSDL_Quit\fP as your \fBatexit\fP call, like: .PP .nf \f(CWSDL_Init(SDL_INIT_VIDEO|SDL_INIT_AUDIO); atexit(SDL_Quit); \&. \&.\fR .fi .PP .PP .RS \fBNote: .PP While using \fBatexit\fP maybe be fine for small programs, more advanced users should shut down SDL in their own cleanup code\&. Plus, using \fBatexit\fP in a library is a sure way to crash dynamically loaded code .RE .SH "SEE ALSO" .PP \fI\fBSDL_QuitSubsystem\fP\fR, \fI\fBSDL_Init\fP\fR ...\" created by instant / docbook-to-man, Tue 11 Sep 2001, 23:00