|
Nemanja Trifunovic wrote: VS6 IDE is lean and fast, but the compiler is way out of date.
Yep, exactly!
Regards,
Nish
|
|
|
|
|
The IDE is fast until you load a large workspace (say about 80 projects). Then it really, really struggles - or crashes entirely.
Anna ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
Currently working mostly on: Visual Lint 
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|
|
You are only thinking of the IDE. The VC++ 6 compiler sucks!!!
Regards,
Nish
|
|
|
|
|
Agreed there too. I can not believe that the highest processor supported in vc6 (without a processor pack which breaks many applications) is the Pentium Pro.
John
-- modified at 9:41 Monday 30th January, 2006
|
|
|
|
|
John M. Drescher wrote: I can not believe that the highest processor supported in vc6
What do you mean by "supported?" Are you saying that it is luck/coincidence that it works with P2, P3, and P4?
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
There is no support or optimization for anything > than pentium pro. No mmx, sse ...
John
|
|
|
|
|
Ahh, that stuff.  I can only guess that since VS6 came out around a year after the release of the Pentium 2, MMX support could not have been included without pushing a bunch of dates back, and since SSE did not come out until almost two years later with the Pentium 3, it could not have been included either. I imagine that Visual Studio Service Packs were not intended to include processor-specific instruction sets.
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
That's NOT about the IDE. that's the fault of the compiler. Let's stay within context here.
------- sig starts
"I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
 But we can leave it at that.
John
-- modified at 12:20 Friday 3rd February, 2006
|
|
|
|
|
The compiler doesn't suck, and I wish you'd stop fuckin' saying that, because it truly pisses me off. It's simply less "compliant" than the newer version. And the *whole thread* is about the IDE.
The VS2002-2005 IDE sucks big hairy donkey shlongs. It's slow. It's cumbersome. It's awkward. MS is trying to force the VB look and feel down our throats, and that's an insult to our intellect. The constant search for how to do sh*t absolutely kills productivity if you're writing real code (un-managed C++).
I'd honestly like to take the VC8 compiler and somehow hook it up to the VS6 IDE.
------- sig starts
"I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Agreed. I will certianlly miss WndTabs when I move to .net. Also, I will miss the ability to organize my classes in folders in the class view. I find this is a real time saver when your project has hundreads of classes. I also use Visual Assist but my version works with .net 2003.
John
|
|
|
|
|
John M. Drescher wrote: I will miss the ability to organize my classes in folders in the class view
I'm not a fan of VS2005 but it does have a "folders" feature, doesn’t work the same as VS6 but its there. The big difference is the folders are no longer children of the project, they exist above it and all of the classes remain the in the project tree even if they are separated into folders.
|
|
|
|
|
S Douglas wrote: I'm not a fan of VS2005 but it does have a "folders" feature, doesn’t work the same as VS6 but its there.
From my point of view, the VS2005 "folders" feature is one of the very few things that really ARE better than in VC6.
I have used the class view folders in VC6 a LOT, and i now use folders in VS2005 too. The Problem in VC6 was that it often lost the folders when the .ncb file got corrupted and a source control provider was installed. I can't count how many times i was redoing the folders in VC6 until i found the "Restore class view"-addin somewhere here on CP.
No problems with lost folders in VS2005, even if the .ncb is nuked away.
I also prefer the VS2005 way to keep all classes on the main branch and putting just references into folders, so i can organize folders and classes in means of the context i'm working in at different times. It is of great help, i can have the same class in multiple folders.
A word on VS .NET overall, all versions: I believe MS has messed the MFC/C++ stuff up on purpose to push developers towards the .Net world.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
