03-26-2008
No sorry to bother you no luck at all
6 More Discussions You Might Find Interesting
1. What is on Your Mind?
If you people find something funny like these go ahead and post it :) (5 Replies)
Discussion started by: vidyadhar85
5 Replies
2. Shell Programming and Scripting
Hello, this is my first post and question. I have search before for this problem but didn't find anything similar.
My case: I have a string inside the variable string1 like this:
string1="lala lele lili lolo lulu"
When I do echo of it, it appears like this:
echo $string1
lala lele lili... (8 Replies)
Discussion started by: hemtar
8 Replies
3. What is on Your Mind?
Just one i like.
Missing Cat! ! ! (0 Replies)
Discussion started by: Action
0 Replies
4. What is on Your Mind?
Guys,
This is funny.
http://i28.photobucket.com/albums/c228/jralph2005/bart.png
jaysunn (2 Replies)
Discussion started by: jaysunn
2 Replies
5. What is on Your Mind?
Annoyances.org - Upgrading to Wife 1.0 (0 Replies)
Discussion started by: jgt
0 Replies
6. What is on Your Mind?
Hello All,
Just want to share some funny *NIX commands :).
$ make love
make: *** No rule to make target `love'. Stop.
On a FreeBSD make:
$ make love
Not war.
$ \(-
bash: (-: command not found
$ man woman
No manual entry for woman
$ touch /me
touch: cannot touch `/me':... (5 Replies)
Discussion started by: RavinderSingh13
5 Replies
LEARN ABOUT OSX
allegro_exit
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)