![]() |
|
![]() |
|
|
Thread Tools | Display Modes |
|
|
#11 | |
|
Programming Guru
![]() ![]() ![]() |
Quote:
__________________
http://jasonpowers.net "There are a thousand hacking at the branches of evil to one who is striking at the root." |
|
|
|
|
|
|
#12 |
|
Expert Programmer
|
There are obviously a few caveats to using MSVC++.
First off what everyone else said sums it up. MSVC is a proprietary compiler, IDE, and set of tools retailed by MS. Many different compilers exits, MingW, GCC/G++, Intel, Borland C++, and the list continues, for the most part all of them compile and work with the eact same code... but here is where thing could get complex when you are working with multiple environments. Different compilers tend to implement C++ to different standard levels, and each compiler even tends to implement their own keywords (MSVC is good at this) or defines. For the most part though you will find a base of keywords and commands defined in the C and C++ standards which should be available (for the majority) across all these compilers. And even when cross compiling your code, you tend not to run into too many problems. If you are using a version of MSVC prior to .net 2002, then you should know that MSVC has actually been really bad at adhering to the standardized form of C++, though as of .net 2002/2003 they have done a really good job at standardizing. One feature that pops out of my mind right now is Partial Template Specializations... G++ is fairly good though at adhering to the ISO standard form of C++.
__________________
Clifford Matthew Roche <geek@cliffordroche.com> Web Hosting: http://www.crd-hosting.com Consulting: http://www.crdev-consulting.com |
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|