Hi all,

I am working together with a team of about 10 developers at a fairly large
Symbian application. The main view of the app has no CBA, only a menu in
the form of a list box (which contains, among other options, an Exit
option). TO make the story short, I've noticed that in the handling of
that Exit option, User::Exit(0) is called. I've read about User::Exit() in
the docs and I can say I'm really confused right now. In the docs it says
that all the resources of the current thread are cleaned up and the thread
is terminated. Indeed, when I exit from this app, there are no leaks and
it exits nicely. Also, none of the destructors are called.

So I wanted to ask when is it appropiate to call this method? I mean, this
seems like the "Holy Grail" of all C++ developers, some sort of a
primitive garbage collector. Why should I write destructors and close
RFs's, when I can simply call User::Exit() at the end and the system will
automagically take care of everything for me?

Are there any Symbian docs that explain this issue? (BTW, I don't know if
it's relevant, but I'm using the Nokia SDK, v. 1.2).

Of course, I've tried to do "the right thing", so instead of calling
User::Exit(), I am calling ProcessComandL(EEikCmdExit) on the app ui.
However, it fails with KERN-EXEC 3, (I've imagined there will be a lot of
leaks, but this KERN EXEC took me by surprise). I've debugged it (I am
using Visual Studio 6.0) and when I am stepping out from the destructor of
the AppUi I am getting this unhandled exception in CONE <some address>.

So if you have any idea what might be wrong, please help me.

Regards!