Code::Blocks vs. Visual C++

[ixfd64]

I've recently switched from Dev-C++ to Code::Blocks, but I use Visual C++ as well. I'm just curious, what are the things that Visual C++ can do that Code::Blocks can't, and vice versa?

Since I sometimes switch between these two, I'd like to know if there are any incompatibilities and such. Thanks.

[ZGitRDun8705]

One advantage of Code::Blocks over Visual C++ is that Code::Blocks can use a wide variety of compilers, including the Visual C++ compiler, whereas Visual C++ can only use Microsoft's compiler.

Another advantage is feature content vs. price.  While Code::Blocks may not yet be as full featured as the Pro version Visual C++, it gets pretty darn close, and for free, instead of $400 US or more.

Yet another is the ability to run Code::Blocks from a portable USB device, so you will always have your customized IDE with you.http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_make_Code::Blocks_portable.3F  Visual C++ is too tightly integrated into the Windows operating system, and impossible to run portably without using Thinstall ($6000 US)

[JGM]

You can also add that code::blocks is cross-platform while visual c++ is for windows only. This opens your market more  :wink:

[Alexis]

Hello all,

I would say the main interest of CB is : it is a thorough stable  free open-source cross-platform IDE with one excellent integrated RAD tool (wxSmith).  I also think CB's text editor is more powerful than VC++ 2005 's one (I don't know VC++ 2008).
I'm still using VC++ 2005 alongside CB to develop under wxWidgets, because of some shortcomings. I'm giving a list to make sure I haven't missed something :

• No multiple selection possible in project file explorer
• No nested virtual folder possible
• No integrated mecanism to detect memory leak - There are dedicated functions for this under VC ++, such as _CrtDumpMemoryLeaks. Thus we need to enable wxWidgets own mecanism (I'm still unable to do it !) or use tools such as Valgrind.
• Cannot divide the main window to display several files at the same files.
• In debugger, variables inside a structure or a class are not seen in watches window.
• Generally speaking, VC++ 's debugger is better than CB's one (in terms of speed, power).

Most of these issues are known, and I'm confident they will be corrected soon !

Regards,

Alexis

[DrewBoo]

I'm just curious, what are the things that Visual C++ can do that Code::Blocks can't, and vice versa?

I'm sure far more people wonder this.  Perhaps these answers deserve a Wiki page.   

Since I sometimes switch between these two, I'd like to know if there are any incompatibilities and such. Thanks.

If you're worried about your actual code being incompatible, that comes down to which Code::Blocks compiler you are using.

If you are using the same compiler between Code::Blocks and Visual Studio, you don't have to worry as long as Code::Blocks and your project are set up properly.

If you are using different compilers you may have incompatibilities, as all compilers vary on how close they come to matching the C++ standard.  Microsoft's compiler in particular is known for permitting code that isn't standard C++ and (less so with recent versions) not being able to compile code that is standard C++.  In this case, your wisest move is to turn all warnings on and keep the warning count at zero, so you don't develop a bad programming habit that one compiler just happens to let slip by.

[ArKay]

I use C::B 95% of the time since editing is a lot easier and the IDE is a lot more helpful than VS, but when I have to debug I fire up VS 2008.