Hi,
So what are the differences between all the different versions of c or c++? I see visual c, turbo c, ansi c, c99, etc. What does it all mean?? If you can name some others that would be good too.
Hi,
So what are the differences between all the different versions of c or c++? I see visual c, turbo c, ansi c, c99, etc. What does it all mean?? If you can name some others that would be good too.
http://en.wikipedia.org/wiki/C99#History
Visual c and turbo c are just compilers/ide
Visual C++ 6 and TurboC are also museum pieces.
I use nothing but Visual C++ 6.
No real reason to change.
I have .net, never use it.
EDIT:
what do you use salem?
Last edited by BobMcGee123; 03-03-2006 at 09:50 AM.
I'm not immature, I'm refined in the opposite direction.
>>No real reason to change.
how bout this as a reason
VC++ POS-Compiler-Crap: Error, the variable 'i' has already been declared.Code:for (int i = 0; i < 10; i++) { //foo } for (int i = 0; i < 10; i++) { //bar }
Well during the week I use two different compilers for the embedded platforms being developed, along with Borland builder and gcc under cygwin (and the code also has to compile with Visual studio as well) for host development.
At the weekend, I use gcc on Linux, and some dev-c++ or gcc under cygwin if I'm in a PC mood.
Plus a collection of museum compilers for that old-time feeling
As you can see, I have no time for "works with this compiler" type of programming (void main'ers take note). I need and use code which is standard C, which has a passable chance of compiling the same on all platforms. It also means on a day to day basis that I don't really care about which compiler I'm using.
> If you can name some others that would be good too.
http://www.compilers.net/
http://www.thefreecountry.com/compilers/index.shtml
>>how bout this as a reason
Never bothered me, I'm so used to it that getting rid of that 'problem' would probably just aggravate me.
>>It may need a few fixes.
Duly noted, although those all seem to be problems fixable in under ten seconds in the stl libraries (meaning, why go out and buy a new compiler/ide if all the major problems are ).
@salem: so, you're a professional programmer. Makes sense that you need the high tech up-to-date stuff with perfect (or as close to perfect) ANSI C specifications. I have no intention of ever going into the professional software development field, my method has always been 'find something that works, and stick to it stubbornly.'
I'm not immature, I'm refined in the opposite direction.
I recognise the second part of that error message but I don't recall ever seeing the first - maybe I need to apply a 'service pack'.Originally Posted by Perspective
I don't think any of the ms compilers handle c99; this from msvc++.net 2003 help:I don't think their latest offering(msvc++ 2005) is any better in this regard - I recall reading something about a lack of customer demand for c99 but, unfortunately, can't provide a link/quote for that.
CProgramming FAQ
Caution: this person may be a carrier of the misinformation virus.
So what was unique about Turbo C and Visual C? What did they do differently? What did "Visual" imply?
Visual C++ was Microsoft's line of compilers. It's IDE had certain features that made the programming process more visual - like a drag and drop form designer, stuff like that. Turbo C++ was Borland's line of compilers. I liked them - but there wasn't anything terribly unique about them. They weren't perfect with the standard, but they were pretty good.
Then don't throw out that DOS PC. But if you ever intend to write programs for Windows, then you're in for an eye-opener.I have no intention of ever going into the professional software development field, my method has always been 'find something that works, and stick to it stubbornly.'
Turbo C and Visual C++ were early IDEs. They packaged the compiler, editor, etc. into a package to make code development easier. These programs have been superceded numerous times by their own later version, but also more recently by better, more standards compliant compilers that are free and can generate code for modern operating systems.
Besides being a marketing term, the "Visual" meant you could do some things such as icon or dialog editing in them too. Easier generation of GUI applications.
IMO/IIRC Turbo C was pretty much obsolete or heading that way by Windows 3.1, and Visual C++ went that way when C++ was standardized in 1998.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
I've read that MSVC6 (and MSVC7.0, but not MSVC7.1) doesnt handle templates correctly, so may have problems with code that implements some advanced template techniques like those used in Blitz++.Duly noted, although those all seem to be problems fixable in under ten seconds in the stl libraries (meaning, why go out and buy a new compiler/ide if all the major problems are ).
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Visual C++ 6 doesn't implement the ISO standard at all correctly (something like 60% I believe?).
Cannot really blame Microsoft for it as the standard was still being finalised when they created it, but enough reason to ditch it for something more recent (like VC2005 and the PSDK, which are about 3 months old instead of 10 years).
Only trouble I've with VC2005 Express on my machine is that it's somewhat unstable and tends to hang when doing things like trying to access the context sensitive help or switching projects, but apart from that it looks and works nicely.
You'll have to get used to using all unicode though for Win32 applications, unless I've missed a setting somewhere that forces 8 bit strings.
Thanks for the replies folks, good info
