You will face criticism on thatOriginally Posted by MarkZWEERS
You will face criticism on that
An even better way: get rid of the console altogether along with the command prompt. Then you won't have to worry about disappearing windows.
You said it XDYou will face criticism on that
The real problem here is Dev-C++. Use Code::Blocks or Visual Studio Express instead. Their developers are not so beset by terminal stupidity that they managed to miss a bug every single newbie ever has encountered for the entire lifespan of the application.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
No, you would still have an output window, whether it is the console or not, and that would have to be closed at program end. Besides, getting rid of the console just because it gets out of your way when it's finished is just stupid, IMO, assuming you're talking about getting rid of it in the system.
But aside from console windows, though, pretty much every windows programmer knows that they must run a message loop or the window will be frozen. So I classify it as quite different from a console window. Don't know if anyone agrees, but oh well.
Nah, no. It has its uses. But not using the prompt for running the applications is what I mean!Besides, getting rid of the console just because it gets out of your way when it's finished is just stupid, IMO, assuming you're talking about getting rid of it in the system.
I think the best solution would be something like what CornedBee was talking about: have an option in the IDE to keep the console open, and have that default to yes.
