lou_dias wrote:
Exactly. I got an A in C and had an A in C++ until the take home final project that we were given a week to work on. I went out of my way to make everything in the situation we were simulating an object. I implemented every object-oriented feature (polymorphism, superclassing, friends...you name it) and it just crashed. Narrowed it down to exactly what made it crash and checked it 20 times and asked others to look at it and noone knew why it just crashed. It was an illegal reference...but it wasn't. I ended up with a B because I failed the final.
That B made me give C++ the F.
So you are telling us that c++ sucks because in your limited
scholastic experience you didnt make the grade you wanted because you couldnt figure out a bug in your program?
This has to be one of the lamest arguments ive ever heard.
Now I happily program database driven applications in VB.Net... which doesn't crash for no apparent reason when I instantiate objects.
This is 2006. Code doesn't have to look cryptic anymore. We have MEGABYTES of RAM to play with not 38k (Commodore 64). It can look pretty and readable and still be fast. Really it can. Honestly, other than uber-geek bragging rights, why settle for C/C++?
To say that any language generally is no good is an absurd statement. When starting a project you first define what the problem is, and how you intend to provide a solution. Every language has it's strengths and weakness. The goal is to pick a language or set of languages that fits. Youve got a lot of things to take into account, legacy stuff, the skill sets of the staff, speed of implimentation, etc. You seem to be doing db stuff, and you have skills with vb and not c, so obviously you went that route. If the boss is happy and you are still getting paid then you made the right decisions.
In a project i'm working on, an embedded device making use of an 8052 microprocessor, we had to pick a language. Our choices were basic, c, or assembler. We rulled out assembler off the top, as there is a lot of float math we need to do and float math in assembler can be very time consuming. We wanted to use basic, as it would make code review go quicker, allowing us to get to market faster, but in evaulating a few basic compilers for 8052 we found that many features we require were lacking. I evaualated several c compilers, picked the one that met our requirements and set out to start development.
And that started out with requirements documentation, implementation dox, flow charts and state diagrams. We have a coding standard, variable names have an order, comments are abundant, and source is peer reviewed. We didnt need to do this because we are writing software in c, we do this because this is how you write software that works. The procedures would have been the same regardless of what language we decided to use. The decade doesnt matter, use the right tool for the job.
[/quote]
And frankly, what makes C++ worse is the people who code in it. You all know who you are. You make your code o ugly, know one would dare modify your original source because no one can freaking read it!
Poorly written vb.net code isnt any easier to read than poorly written c code.
