Compiling and running
Most of the time you’ll be compiling and searching for your own errors.
When compiling your project, you want to look at problems as they appear even if it continues compiling. Most of our candidates handles this very well. There are differences though and they can help you if they work for you.
Eclipse has a line of tabs at the bottom by default. These can be customised and Eclipse can keep going even when you’re handling other problems. The organisation you can achieve while debugging is great and it links you to the place in the source code.
The latest version of Netbeans (12.0) has no support for either C or C++. However, if you add the Netbeans 8.2 plugin portal, you can install the old features for C and C++. Compiling is fast, but finding your way to solutions is less obvious. You’re unable to compile in Pycharm. However, you have the execution window and the Python console. There’s also an R console. All the necessary tools are located at the bottom of the screen.
Qt Creator requires that you put a little more effort into finding the libraries and knowing your qmake. Otherwise, you set it as usually. You’re directed towards Qt libraries of course, but don’t let that stop you if you prefer Qt Creator over the other IDE offerings.
Finally, Code::blocks has a standard compiler, but that’s just a choice that you make during the installation process. You can add any compiler yourself. Results and logs are neatly presented at the bottom.
All five IDES do a great job of presenting your compile. However, Eclipse offers quick fixes and so takes the win here.