Quote:
|
How about this: it is the best supported windows compiler out there. As soon as gcc gets all the point and click UI stuff that VC++ has, I will switch in a second.
|
I thought you were talking about the compiler itself being the best compiler, which I have problems with because the Visual C++ compiler has issues with standards compliance. As for the GUI, there are several nice ones that work on top of GCC. GCC itself is just a compiler, just like the command line compiler that's part of VC++. Personally, one of the biggest benefits for me with GCC or other compilers is that I
don't have to use the bloated user interface. I greatly prefer the ease of use and flexibility of a good editor (nedit) and Makefiles coupled with a command line, but that's just me.
Quote:
|
With the way windows does handles, it is still possible to have resources allocated after a program quits.
|
If this is true then that sounds like (yet another) Windows bug. (I can't say that I know much about Windows GUI programming; I try to avoid Windows as much as possible.) A true OS would never allow a user process to allocate memory that can never be recovered, no matter how the application is terminated.