view docs/man3/SDL_Quit.3 @ 2701:91b0e95f443a

Date: Wed, 7 May 2008 21:48:10 +0200 From: Christian Walther Subject: SDL 1.3 Xcode projects Here are my promised updates to the Xcode projects. They work as far as I'm using them, but I have not tested them thoroughly, and there may still be some cruft left. In particular, I haven't checked whether the frameworks still work on older versions of Mac OS X (are we still targeting 10.2?), and whether Altivec/SSE optimizations are properly done. Of note: I incremented the framework version to B to enable SDL 1.2 and 1.3 to coexist in a single framework. Let me know if you see any problems. Greetings Christian
author Sam Lantinga <slouken@libsdl.org>
date Thu, 08 May 2008 05:06:24 +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