Thing is, I can't work out how much of that is due to his poor English. You can't fault people for not speaking English natively.
So let's try to keep it civil, shall we?

You do, but that wasn't my point.
What you need to take away from that bit of text is mostly from part 5 onward. In particular you should:
1. Make it clear what you're trying to do
2. Make it clear what teh code you have does
3. Make it clear why this is different from what you want it to do
4. Don't expect people to wade through hundreds of lines of source code
5. Think about what people say, ask if you need more help
6. Change your wording if people do not understand your question. Consider posting the question in your own language as well as in your best English; chances are someone will understand it.

I would also strongly recommend that you invest some time in improving your English. Try reading some English texts or books, or watch English movies/television (with subtitles). You'll need a dictionary for reading at first, but I think it's the best way to learn.

I cry Punk!

What Evert was thinking ( For the closing part )

What does not work with the ESC key, can you test that attached code, a b ?

Have you really tried what all the others have said ?

Test the attached binary to see if this code do what you want.

Follow Evert's last advisement: there are enough examples and documentation in the allegro library distribution to make you understand how it works (it's commonly the case)

_

There are so many things wrong with this sentence ...
Firstly: It's not my idea. That's what I do and that's what I told you to do, but it's pretty much standard AFAIK; set a flag that signals the game is running, and run the game as long as the flag is true.
Secondly: like I said, it's standard. That means it does work. You're not an exception in this sense. Programming is logical, the same rules apply everywhere. We're not taking guesses at how to do what you want (although we are guessing what exactly you want), but we're telling you how to do it. We've done it before, the advice given and code posted in this thread is all valid.
Finally, the reason nothing happens when you press ESC is that you have an infinite loop. Any code outside that loop will never be executed, hence the game will never end. You say you can't do what I suggested, since you have another function after meni(). Why? Why do you have a function call you never want to be executed? Please tell me why! If you can't answer that, there's absolutely no helping you.

You can't just call function after function and zip from one procedure to the next. It'll look horrible and it won't work. You have to use states. That is: if your game is in the menu state, call the menu function. No loop inside the menu function, just call it once. If the game is still running, it'll loop over and the function will be called again. Same thing for every state your game can be in. LennyLen already provided basic example code for this. If you do that, all the problems you have addressed so far will pretty much be solved. If you refuse to do this, I refuse to help you.

For the love of *(&#*@# stop using key[] already!
If you don't want to block with readkey(), use keypressed() first to check if there's a key in the buffer.

Look up flow control and loops in your favorite C book and get rid of those goto statements.

He has no understanding, that's the problem.

it "sucks" not knowing English. you will not find the right meaning for words like "sucks" in you translators.

send me your project file zip if your using msvc++6 ill fix for you so you can move on

edit its 2007 why are there no browser to bridge language bearers yet(like star track)

here is one ways to fix

this is what i change
else if(key[KEY_ESC]){break;} //old

to

else if(key[KEY_ESC]){exitexit();} //new

EDit:
sorry i could not compile it because i do not have that compiler.
is that what you wanted it to do

the problem was the trance of the manual. this is how it went down you was looking for things to do keyboard input. so you found readkey(); and key[]. what you did not trance is that they both are tools to do the same thing in 2 different ways. thats why you combined them.

int val;
val = readkey();

if ((val >> 8) == KEY_ESC){exitexit();} /* by scancode */

same thing

if(key[KEY_ESC]){exitexit();}

interpretation

quote: they both are tools to do the same thing in 2 different ways.

What do you mean by same thing?

One waits for a key to be pressed and returns which key it is,
the other one returns the state of a key. That's not the same thing.