Mercurial > sdl-ios-xcode
annotate docs/man3/SDL_Quit.3 @ 93:fc774f445e10
Applied Hannu's fix and switched to blocking writes .. seems to work?
author | Sam Lantinga <slouken@lokigames.com> |
---|---|
date | Sat, 07 Jul 2001 23:27:29 +0000 |
parents | 55f1f1b3e27d |
children | e5bc29de3f0a |
rev | line source |
---|---|
55
55f1f1b3e27d
Added new docs for SDL 1.2.1
Sam Lantinga <slouken@lokigames.com>
parents:
0
diff
changeset
|
1 .TH "SDL_Quit" "3" "Sun 10 Jun 2001, 19:41" "SDL" "SDL API Reference" |
0 | 2 .SH "NAME" |
3 SDL_Quit\- Shut down SDL | |
4 .SH "SYNOPSIS" | |
5 .PP | |
6 \fB#include "SDL\&.h" | |
7 .sp | |
8 \fBvoid \fBSDL_Quit\fP\fR(\fBvoid\fR); | |
9 .SH "DESCRIPTION" | |
10 .PP | |
11 \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: | |
12 .PP | |
13 .nf | |
14 \f(CWSDL_Init(SDL_INIT_VIDEO|SDL_INIT_AUDIO); | |
15 atexit(SDL_Quit); | |
16 \&. | |
17 \&.\fR | |
18 .fi | |
19 .PP | |
20 .PP | |
21 .RS | |
22 \fBNote: | |
23 .PP | |
24 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 | |
25 .RE | |
26 .SH "SEE ALSO" | |
27 .PP | |
28 \fI\fBSDL_QuitSubsystem\fP\fR, \fI\fBSDL_Init\fP\fR | |
55
55f1f1b3e27d
Added new docs for SDL 1.2.1
Sam Lantinga <slouken@lokigames.com>
parents:
0
diff
changeset
|
29 ...\" created by instant / docbook-to-man, Sun 10 Jun 2001, 19:41 |