Mercurial > sdl-ios-xcode
view docs/man3/SDL_Quit.3 @ 866:0a45995a7fc3
Date: Tue, 2 Mar 2004 11:34:54 +0100
From: Bartosz Fenski aka fEnIo
Subject: outdated entry in INSTALL file
I've just found in INSTALL file:
If you are cross-compiling from Linux to Win32, you should read
the file README.Win32
But you don't shipped this file with SDL. I've found in CVS logs that
this file has been deleted and this information is now in FAQ.
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Tue, 02 Mar 2004 13:01:02 +0000 |
| parents | e5bc29de3f0a |
| children | 546f7c1eb755 |
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