Thread: How to avoid console program crash when terminated too early

Hi ho,

I've just started working with C++. But I do know C# already, so it shouldn't be too much of a problem. Anyway, when you create a console program, and it's terminated too early because the user closed the window, it returns an error. My Borland/CodeGear C++ Builder even crashes, which is extremely weird (when I used to work with C#, whatever happened with the program, Visual Studio 2005 itself would never crash).

Can anyone help me with this?

Thanks in advance,
Xargo

Are you sure the crashing of the program itself, even in standalone mode (without debugging or whatever), when the user closes the console, is because of the CodeGear/Borland IDE? I've actually seen many console applications do this. Especially small C++ programs, mess it all up when the user terminates the console manually (had it many times with several C++ console applications made by several programmers).

If they'd all do this, it's ok, then it's just cuz it is like that. But for example C# doesn't have that problem. Of course C# is built on the .NET Framework, but does that matter? If C# is capable of doing it, why not C++?

I think this is just a misunderstanding of Windows' behavior when it comes to the console. If you manually close the console while it is running an executable, then in order to do what you expect the console has to quit everything it's doing in a hurry. Often this gets interpreted as an error with the console because that's pretty much all Windows knows about the actual executable you tried to run, and it doesn't really know what else to do about the exit status that was returned from *your* C++ program.

C++ is not part of the .NET framework because the language predates it. I admittedly know nothing about the .NET framework, but it really has nothing to do with anything in this case.

Originally Posted by citizen

I think this is just a misunderstanding of Windows' behavior when it comes to the console. If you manually close the console while it is running an executable, then in order to do what you expect the console has to quit everything it's doing in a hurry. Often this gets interpreted as an error with the console because that's pretty much all Windows knows about the actual executable you tried to run, and it doesn't really know what else to do about the exit status that was returned from *your* C++ program.

Owkay, thanks for the information.

Originally Posted by citizen

C++ is not part of the .NET framework because the language predates it. I admittedly know nothing about the .NET framework, but it really has nothing to do with anything in this case.

If the C++ I'm doing right now would be .NET I won't even waste my time on it. The reason I am doing C++ now, is because I want to get rid of the dependance of the .NET framework, which makes your app exclusively for Windows XP and higher. (A pity though, .NET is actually quite nice. If Microsoft would only be working a little more open-source-ish, more cross-platform-ish, and less-monopoly-ish; I would use .NET for almost everything. Although it still has some disadvantages of course (like performance).)

By the way, you do know that C++.NET also exists?

Originally Posted by CornedBee

All I'm saying is that if Borland crashes if you close the console your program is running it, that's a Borland bug. There can be absolutely no doubt about it, and it has really nothing to do with the C++ program.

Ok.