I'm using Visual C++ version 6 right now, but I also have Visual studio Dot Net (version 7) on cd. A friend told me I can stay with Visual C++ ver 6, but what do you think? Shall I stay with v.6 or go to v.7?
I'm using Visual C++ version 6 right now, but I also have Visual studio Dot Net (version 7) on cd. A friend told me I can stay with Visual C++ ver 6, but what do you think? Shall I stay with v.6 or go to v.7?
Go with the later version, the standards compliance of vc6 pretty much sucks.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
The time when you go to v.7 is when you realize why it's better ( on your own ).
lu lu lu I've got some apples lu lu lu You've got some too lu lu lu Let's make some applesauce Take off our clothes and lu lu lu
Poseidon - God of the C ? Really I thought it was the thunder ? Or was it ... This is stupid!
lu lu lu I've got some apples lu lu lu You've got some too lu lu lu Let's make some applesauce Take off our clothes and lu lu lu
http://en.wikipedia.org/wiki/Poseidon
Are you mixing up your Greek and Roman gods? Tut tut
Well, version 7 sucks less than version 6. If you can manage to get an upgrade to .NET 2003 (version 7.1) get that -- 7.1 is an incredibly good compiler. 7 is only okay, but better than 6.Originally Posted by ThWolf
Last edited by Cat; 08-21-2006 at 04:03 PM.
You ever try a pink golf ball, Wally? Why, the wind shear on a pink ball alone can take the head clean off a 90 pound midget at 300 yards.
.NET 2005 is excellent. 2003 is also good. You'll be converted simply by using either one. It took me about 1/2 an hour to fall in love. There's a little BS to get used to but hey, thats the way it is in any new relationship.
"There's always another way"
-lightatdawn (lightatdawn.cprogramming.com)
I got VS6.0 and VS.Net 2003 both on my machine. After I installed 2003 I hardly find myself launching VC++ 6.0 anymore and if I do it by "accident" (you know, when youre too tired in the morning and only reflexes are operational) my first thoughts are "what is this ........"?
Just install .net, it doesnt break your old vc installation (atleast it did not do it to me) and see for yourself
Ok it was the sea god, i knew that ... ( maybe )
lu lu lu I've got some apples lu lu lu You've got some too lu lu lu Let's make some applesauce Take off our clothes and lu lu lu
I was a bit anxious when I made the move from VC6 to 2003, all those years ago (like 2). I'm glad I did though.
Echo Rennor.
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
I haven't made the switch yet. Probably for the same reason that I haven't stepped foot inside a McDonalds for over 15 years now...
Superstition.
(Well, the McDonalds thing was due to being served a soggy burger when I was young and impressionable)
In most cases I like to target all Windows platforms, including Windows 95. Some of these are incompatible with the .NET platform, so I wouldn't like to introduce code changes that would rule those targets out.
That's not to say that I wouldn't wanna use it, I mean, given that Windows is supposedly going to move to a situation where .NET code is ran "natively" and unmanaged code is ran in some sort of managed VM.
ISO compliance isn't such an issue when you code in pure C.