VC6 vs VC7 (2003)

This is a discussion on VC6 vs VC7 (2003) within the C++ Programming forums, part of the General Programming Boards category; Has anyone noticed any compile time difference between these two compilers? It seems like VC2003 takes a lot longer to ...

VC6 vs VC7 (2003)

Has anyone noticed any compile time difference between these two compilers? It seems like VC2003 takes a lot longer to compile for me. I haven't done any extreme comparisons yet. Have you noticed any difference?

I have noticed that mine seems to take forever to just start running a program from within the IDE unless I choose the "without debug" option even if there are no break points set or watches, etc... By forever I mean it seems to take about a minute for the program to simply start whereas if I choose "without debug" it runs immediately. VC6 will run a program immediately regardless of whether it is just execute (CTRL+F5) or Start Debug (F5).

"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens

"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens

That's just one guys information. I strongly urge you to do your own timings. Who knows what compiler settings he was using for .net 2003. I'm pretty certain that it performs incremental linking correctly when enabled.

I'm pretty sure .NET 2k3 shows the compile time by default (or an easy to find option), but the one for VC6 is undocumented I believe. You simply add /y3 to the command line startup of the shortcut and you should be good to go. Do your own research, you might be suprised with the findings.

"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers

I'm pretty sure .NET 2k3 shows the compile time by default (or an easy to find option), but the one for VC6 is undocumented I believe. You simply add /y3 to the command line startup of the shortcut and you should be good to go. Do your own research, you might be suprised with the findings.

"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers

"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers

Works for me, a few posts ago I copy and pasted my "Target" box string exactly the way I have it on my machine. Make sure it's outside of the quotes, if it's inside then you will receive the error msg you described.

"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers