Using Visual C++ 6

Because it still suffers from all the bugs and potential security holes that were fixed in the last 14 years.

Because you're almost certainly trading better compilation time for worse run-time performance by giving up over a decade of compiler improvements.

Because your pre-standard compiler has you writing code that isn't even valid C++, and working around issues that are long-since fixed.

Because a newer standard library reduces development time.

Performance?
I have tested my game apps with several ides and best performance was shown in vs6, worst in vs2008 allmost 1.5 time slower, with same compilator options.
Ofcouse c++ is not nowadays standart.

Windows 98 would offer best performance over windows 7 on my hardware, why not use it?
Its obsolete?


The C++ your writing in VC++6 technically isn't valid C++ anymore, the actual compiled code will be far less optimised than using the modern GCC.

Guy above, C++ is now standardised, VC++6 is not compliant. GCC is. And its a compiler, not compilator. If your code is running faster in VC++6 then it means your code is being written in the non standard C++ used by it and probably optimised for that compiler, go run actual C++ code through it and it WILL be slower at run time.

Aside from the above, some day your code is just no longer going to run. I know of projects originally built with VC6 that crash and burn horribly on 64-bit Windows 7; a simple and minimal port to VC2008, a quick recompile later, and they work perfectly again.

You can put off a move to a more modern environment until the bitter end, and then find yourself having to do an emergency upgrade that you'll most likely make a mess of the first time.

Or you can start a sensibly phased upgrade now and have everything nice and clean.

Your choice.

Ofcouse c++ is not nowadays standart

C++ was standardised in 1998, after the release of Visual Studio 6. Code that does not follow that (or one of the two more recent C++ standards, in 2003 and 2011) is not considered to be valid C++.

Thats the point of standart if the same code compiles on vs6 and on vs2008 with no changes in code.
So is my code standart c++, if compiles on both?

The point isn't if your code compiles, it's whether or not standard code will compile on your compiler. Trust me, there is plenty of perfectly standard code that VC6 will choke on like a baby eating a jawbreaker. You're using an obsolete and provably broken tool. If you want to convince yourself that your reasons for using it aren't stupid, that's fine. Just don't expect the rest of us to think you're anything other than an idiot.

why are you guys getting sore about this?Just let the guy use whatever he wants, at the end, is the results that counts and this guy isn't doing anything to write home about, so let him waste his time however he wants.
Now, if a new great game came out and was compiled with VC6 that would be news, but a random dude on a forum convinced that VC6 + DX7 is the nirvana of computing? Who cares?
This just goes into the same category of the heroes that show up in every IDE thread claming they write all their software with VIM + command line.. and then you discover they write 1000 lines of code per year.. .

Programmers resisting innovation and progress is such a contradiction, I never stop getting amazed watching them.

If your code *compiles* more slowly using a modern IDE, its probably because your hardware is outdated, but if your code *runs* more slowly after being compiled by a more-modern compiler, then you are either overlooking settings that should be used, or you're writing in a VC++ 6-era code style. Modern, standard-compliant, idiom-embracing code should most-definitely run faster after being compiled with a modern compiler.

I mean honestly, VC6's knowledge of processor architecture probably stops around the PIII and Athlon (if you've got all the service packs) for starters. You're at the very least leaving 10+ years of new, efficient instructions on the table.

why are you guys getting sore about this?Just let the guy use whatever he wants, at the end, is the results that counts and this guy isn't doing anything to write home about, so let him waste his time however he wants.

Absolutely, but given he asked the question I feel it's best to at least try to explain our objections. :-)

(Posted from mobile.)

Pretty sure I read somewhere that Dx7 and 8 aren't even supported on windows 8 anymore, probably wrong, then again why would they support it?

Pretty sure I read somewhere that Dx7 and 8 aren't even supported on windows 8 anymore, probably wrong, then again why would they support it?

And what makes you think Windows 8 will ever be used on the guy's system

I've had to port code from VS6 to 2005, there were so many issues.

But I agree, if this guy finds that he can do what he needs to for his personal enjoyment using VS6 then so be it.

why are you guys getting sore about this?Just let the guy use whatever he wants, at the end, is the results that counts and this guy isn't doing anything to write home about, so let him waste his time however he wants.

It's not getting sore. If you go anywhere in IT asking for help, and if you're on an obsolete, unsupported and demonstrably broken platform, the first thing to do is get you onto one that's reasonably up to date and sane - chances are that on it's own will fix your problems.

Besides, the attitude of the OP was that it would be a good idea to be using VC6 (as well as explicitly asking why not to use it). If he had said something on the lines of "I'm still using VC6 and it works for me, despite issues like P0, P1, P2, ... and P compared to a modern tool" then hardly anyone would have had a problem with it. Everyone needs some kind of hobby.
Personally I do not have a problem with that hobby being (figuratively) sleeping in a bath tub full of deadly scorpions (provided care is taken the scorpions don't get injured or can escape to harm nearby innocents). I do object to someone saying sleeping in a bath tub full of deadly scorpions is a good idea and everyone should be doing it.

Lol i would only use it if I had to use it.... Targeting win95 or win32s if oh god some people remember that far... Did vc6 still generate windows 3.1 binaries?

Another reason to use it is if you have to use it. I taught a vb class recently and department told me not to use modern vb.net. Book also used old vb and provided vb working model. So sometimes classes are taught using classic versions of the language.