Is it time to say goodbye to VC6 compiler?

Question

Of late I\'m facing the issues that points finger to VC6 compiler.

Few of them are:

1. A function-try-block doesn\'t work. Related Q
2. in-class constan

Answer 1

Well, here's the thing. The VC6 compiler sucks. However... the IDE is pretty good.

VS2005 has much better source control support. Otherwise, it's much slower debugging, has a crappy output pane that exponentially decays on inserting output lines (what absolute garbage coding is that?), the help system is many times slower, and debug and continue (possibly Microsoft's best feature over other IDEs) is considerably more broken.

.NET? Sure, VS20xx is the only way to go. However, for one small client that is sticking with VC6/MFC (for interfaces to embedded systems, etc) I actually enjoy working with VC6. It's just FAST.

2008? I'd like to... but it takes a while for my clients to migrate. Nobody has, yet.