What is your favourite IDE?

[emadsen]

I don't know why people like so must to have debugging capabilities.

Because it's practically free if you're already using a robust IDE like VS, Netbeans, Eclipse, etc. For very little cost you get great benefits: a view of the internal state of your program with zero modifications to your code.

If you're not working in an IDE, then yes, there are costs (perhaps financial, certainly time/frustration to learn a new tool). The costs may not be worth the benefits. But for me the cost of the debugger is zero.

[stegemma]

I use CodeLite me too. I come from Borland C++ Builder, that was great for windows programming but i don't like the CodeGear/Embarcadero evolution of that IDE. I've tried:

Code::Blocks: too hard to configure and not stable under Mac, in my tests

Eclipse: good but too many complex to install and configure, hard to make it works well both in Windows and Mac (for me it worked well on the Mac, not in Win)

Visual C++: very good system but only for Windows

Some other ones: someone works good in Windows but not in Mac, someone the opposite, someone doesn't works at all

In my situation, i have sources that i have to compile with Borland C++ Builder. They are fully portable to Mac/Linux/Symbian but i need to keep the c++ files on a Windows machine. My new programs are developed in a portable way, using wxWidgets, primarily on a Mac machine. My goal was to have projects fully portable across platform (Win+Mac, maybe Linux). I would like just to copy the folders of the sources from Windows to Mac and viceversa and then compile, without having to manually adjust configurations or paths every time. This could be achieved, in my experience, only with CodeLite and some little work on system variables, for root paths and some other little thing.

[lucasart]

I use CodeLite me too. I come from Borland C++ Builder, that was great for windows programming but i don't like the CodeGear/Embarcadero evolution of that IDE. I've tried:

Code::Blocks: too hard to configure and not stable under Mac, in my tests

Eclipse: good but too many complex to install and configure, hard to make it works well both in Windows and Mac (for me it worked well on the Mac, not in Win)

Visual C++: very good system but only for Windows

Some other ones: someone works good in Windows but not in Mac, someone the opposite, someone doesn't works at all

In my situation, i have sources that i have to compile with Borland C++ Builder. They are fully portable to Mac/Linux/Symbian but i need to keep the c++ files on a Windows machine. My new programs are developed in a portable way, using wxWidgets, primarily on a Mac machine. My goal was to have projects fully portable across platform (Win+Mac, maybe Linux). I would like just to copy the folders of the sources from Windows to Mac and viceversa and then compile, without having to manually adjust configurations or paths every time. This could be achieved, in my experience, only with CodeLite and some little work on system variables, for root paths and some other little thing.

I use make/gcc under Linux, and generate windows executables without even having windows on my cvomputer. I don't even test it and people confirm that it works perfectly under windows. Now that's portability
Why would I yuse as many operating systems and IDE as I wnat to produce targets? I'm not going to have a Mac, and a dual boot PC with Windows and Linux, just for that...

I do not use the IDE to compile my code. I only use it to write the code, because it's nice and pretty, and debugging is easier. Then I compile all the targets I want with a simple command line. Simple portable and efficient.

[stegemma]

...

I use make/gcc under Linux, and generate windows executables without even having windows on my cvomputer. I don't even test it and people confirm that it works perfectly under windows. Now that's portability
Why would I yuse as many operating systems and IDE as I wnat to produce targets? I'm not going to have a Mac, and a dual boot PC with Windows and Linux, just for that...

I do not use the IDE to compile my code. I only use it to write the code, because it's nice and pretty, and debugging is easier. Then I compile all the targets I want with a simple command line. Simple portable and efficient.

Because i come from an integrated compiler+editor i'm a little lazy and i don't want to do manual steps, if i can avoid them. I must use (even) Windows because a lot of old software are still in use and they are Windows applications.

With CodeLite + mingw32/g++ i compile on Windows and with CodeLite + g++ i compile on Mac. I think that this could be done the same on Linux, but i've never tried CodeLite in Linux.

The IDE simplifies debugging and it have some feature to handle projects and various options. This makes me speed up my work, i think, because i have to finish Satana before october.

If i would have more time, i would have to write my own IDE... but i have no time at all and CodeLite is a good choice: simple and stable.

[stegemma]

Some time a good local variables view can show you bugs that you don't expected to have. Just today, i've found a bug in Satana just seeing that a variable gets the value 2999000 or something similar. If i expected that kind of bug in the use of that variable maybe i could use std::cut to see it... but the bug was i was searching for so only in the debugger i have early find those error. (sorry for my english... i think to have misspelled almost all, in this reply ).

[Mpsey]

Microsoft Word