VC++ sucks.
-
It's funny, I accidentally corssposted into comp.lang.java.advocacy with the comment 'java sucks' a few months ago. I wasn't trolling like this anonymous clown, I was actually talking about languages to do graphics in, the user had asked about java ( hence the cross post I did not see ). I must say that we are a far more restrained lot than the guys ( and gals I s'pose ) on c.l.j.a. Talk about starting a firestorm...... To the clown who started the thread - have the guts to put your name to your posts, and the intelligence to either present your case if you want to discuss it, or shutting up and going away if you're just looking for attention. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
-
-
John Robbins excellent book 'Debugging Windows' tells you how to figure what line of code you crashed on using the disassembly window. It also tells you how to write crash handlers and lots of cool stuff. It's not just about how to push F10 and F11 in the debug Window ( like the useless 'Desigining user interfaces' book, has anyone actually *bought* that. No weait, don't tell me. ). Anyone who doesn't have this book should buy it. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
Christian, do you mean "Debugging Applications" by Robbins? That was the only one I saw on Amazon.
-
I've only recently started playing with it, and like most such tools it has it's good points and it's bad. I find it anoying that with a very small ammount of use I've been baffled by two unrelated compiler faults and one, shall we say, infelicity of design in MFC which meant going all round the houses to do something which ought to be trivial (replacing one of the windows under a splitter). There seems to be a certain ammount of too clever by half about MFC. Fancy techniques used where simple techniques would have been more flexible. I find much of the documentation nearly useless, being formulaic in nature when it ought to be explanatory. It's also irritating that the class references are on CDROM and take forever to acccess (it also interferes with my listening to music while I hack). On the other hand I find the IDE surprisingly useful. Compiler errrors tend to be vague but runtime errors are quite well handled. The debugger seems quite good (is there an "evaluate expression" anywhere?).
-
I've only recently started playing with it, and like most such tools it has it's good points and it's bad. I find it anoying that with a very small ammount of use I've been baffled by two unrelated compiler faults and one, shall we say, infelicity of design in MFC which meant going all round the houses to do something which ought to be trivial (replacing one of the windows under a splitter). There seems to be a certain ammount of too clever by half about MFC. Fancy techniques used where simple techniques would have been more flexible. I find much of the documentation nearly useless, being formulaic in nature when it ought to be explanatory. It's also irritating that the class references are on CDROM and take forever to acccess (it also interferes with my listening to music while I hack). On the other hand I find the IDE surprisingly useful. Compiler errrors tend to be vague but runtime errors are quite well handled. The debugger seems quite good (is there an "evaluate expression" anywhere?).
In this age of 40 gig drives, you'd be mad not to have the MSDN fully installed on your hard drive. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
-
In this age of 40 gig drives, you'd be mad not to have the MSDN fully installed on your hard drive. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
So when was the old law: Files expand to fill the space available repealed?;) Actually it's probably just parsimonius habbits (that, and having three separate opertating systems).
-
John Robbins excellent book 'Debugging Windows' tells you how to figure what line of code you crashed on using the disassembly window. It also tells you how to write crash handlers and lots of cool stuff. It's not just about how to push F10 and F11 in the debug Window ( like the useless 'Desigining user interfaces' book, has anyone actually *bought* that. No weait, don't tell me. ). Anyone who doesn't have this book should buy it. Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.
My boss did - nuff said? X| !! Andy Metcalfe - Sonardyne International Ltd
(andy.metcalfe@lineone.net)
http://www.resorg.co.uk"I used to be a medieval re-enactor, but I'm (nearly) alright now..."
-
Christian, do you mean "Debugging Applications" by Robbins? That was the only one I saw on Amazon.
Yes, sorry :) Buy it, buy it, buy it !!!!! Christian #include "std_disclaimer.h" People who love sausage and respect the law should never watch either one being made. The things that come to those who wait are usually the things left by those who got there first.