allegro_exit(3alleg4) [suse man page]

allegro_exit(3alleg4)						  Allegro manual					     allegro_exit(3alleg4)

NAME

       allegro_exit - Closes down the Allegro system.

SYNOPSIS

       #include <allegro.h>

       void allegro_exit();

DESCRIPTION

       Closes  down  the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines
       have been installed. You don't normally need to bother making an explicit call to this function, because allegro_init() installs it  as	an
       atexit() routine so it will be called automatically when your program exits.

       Note  that  after  you  call  this function, other functions like destroy_bitmap() will most likely crash. This is a problem for C++ global
       destructors, which usually get called after atexit(), so don't put Allegro calls in them. You can write	the  destructor  code  in  another
       method which you can manually call before your program exits, avoiding this problem.

SEE ALSO

       install_allegro(3alleg4),    allegro_init(3alleg4),    destroy_bitmap(3alleg4),	  ex3d(3alleg4),    exscn3d(3alleg4),	exswitch(3alleg4),
       exxfade(3alleg4), exzbuf(3alleg4)

Allegro 							   version 4.4.2					     allegro_exit(3alleg4)

allegro_exit(3alleg4)						  Allegro manual					     allegro_exit(3alleg4)

NAME

       allegro_exit - Closes down the Allegro system.

SYNOPSIS

       #include <allegro.h>

       void allegro_exit();

DESCRIPTION

       Closes  down  the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines
       have been installed. You don't normally need to bother making an explicit call to this function, because allegro_init() installs it  as	an
       atexit() routine so it will be called automatically when your program exits.

       Note  that  after  you  call  this function, other functions like destroy_bitmap() will most likely crash. This is a problem for C++ global
       destructors, which usually get called after atexit(), so don't put Allegro calls in them. You can write	the  destructor  code  in  another
       method which you can manually call before your program exits, avoiding this problem.

SEE ALSO

       install_allegro(3alleg4),    allegro_init(3alleg4),    destroy_bitmap(3alleg4),	  ex3d(3alleg4),    exscn3d(3alleg4),	exswitch(3alleg4),
       exxfade(3alleg4), exzbuf(3alleg4)

Allegro 							   version 4.4.2					     allegro_exit(3alleg4)