Today is your lucky day, it's available for free at http://clang.llvm.org/ and http://valgrind.org/.
Make sure you read the instructions before you start, though. You can find them at http://www.amazon.com/Programming-Language-2nd-Brian-Kernighan/dp/0131103628.
Enjoy!

This is the second example I've run into today of someone running around with a programming language looking for problems to solve.
How are you supposed to be able to contribute anything of value if you don't even use the tool yourself? You'll end up gold plating your way to being banned from the mailing lists in no time at all.
Write something you need, something you care about.

Sorry, can't do that.
In Sweden we mainly play what you refer to as 'Soccer', but we call it 'Fotboll'.
I guess we could start calling the other kind 'Soccer' to add some spice to future international communications...

Sure, DoF decreases with larger apertures. But if you're trying to minimize blurring by going with a shorter shutter you will end up with a larger aperture to get enough light in there.

A quick glance at planet.perl.org says you're talking out of your ass. Perl offers a mature language, an experienced community and an unmatched repository of reusable libraries.

I agree the language is easy. But, using it correctly and responsibly isn't. C is like Lisp in that there are no artificial limits on what you're allowed to do. Not all solutions are equal though and it takes experience and good taste to choose the right path.

Everyone is already doing namespaces in C, nothing new here but syntactic sugar.

I typically use three types of data structures in my C code, a vector type that stores pointers, a hash type that maps pointers to pointers (remember that a string is a simple pointer in C), and a set type that stores pointers. All this without any ugly macro hacks. Not as 'safe' as the generic variants but safe enough and a lot easier on the eyes.

They're nice features, and two good examples of features that a lot of C-programmers wouldn't mind being added to the language. But they are not a good enough reason to choose C++ considering the complexity price.

Oh, come on! How old are you? 18 tops? Calling everyone who disagrees with you undereducated whiners is going to take you nowhere in life.

C++ does a lot of stuff under the covers and if you don't understand exactly what it's doing it's going to come back and bite you badly. What I (and a lot of other people) am arguing is that it's a bad trade-off, that it's easier to do the chores yourself than to make sure C++ only does exactly what you want it to.

And finally we find something we agree on.
Only that's what a lot of people, including the GCC folks, are pretending. That it's nothing but C with extra sugar on top.

But C++ isn't a higher level language, they're not gaining anything but hidden complexity.
The low level knowledge you have to possess to use the high level features correctly make them practically useless and you often end up spending more time coaxing the language to do the right thing than you would have spent writing the code yourself.

I can assure you that whatever it is that's holding the project back it has absolutely nothing to do with a lack of language features.
Everything that should be done in C++ can be done easier and simpler in C by reasonably competent programmers, the rest of C++ is pure madness and it will slowly seep into the project regardless of coding standards.

Well fuck you too!

I'm 33, been writing code daily since I was eight, I started doing C++ around 18, really bought into it, and finally gave up and moved on around 28. I've been there and done that. I've seen projects grind to a halt while people are busy painting their multi-paradigm bike sheds.

There is no anti-C++ dogma here, only sharing of hard won experience.

The C++ I've learned and am trying to forget does a hell of a lot more than standardize the OOP boilerplate, give C++ a finger and it'll eat you and your family.
They will spend all of their time arguing about const &this and virtual destructor that instead of solving real problems until nobody really cares anymore.
The life so short, the language fucking impossible to learn.

If they feel they've got to improve their architecture, fine, do that. There's nothing magical in C++ that will make their code better, only more complex.

And about LLVM and the bad old days, that's not really what's happening.
What *is* happening is that the most commercial and proprietary company I know of is using it's resources to develop open source compiler technology.

Great idea! This will surely help steal back users from LLVM/clang. The reason people are jumping ship is because they want a compiler written in C++, it has nothing to do with performance, licenses and/or features. Just thinking about those crunchy templates, page up and page down, makes my mouth water. I can't even begin to comprehend how they ever got anything done without templates.

Anybody care to provide the complete address for Apple HQ? I plan to send back my fully functional iPhone 3G in it's box with this note: To Mr. Steve Jobs. Enough is enough, fuck you and your moral responsibilities! I've bought my last Apple product. Sincerely, ... English is not my native language so if I did something wrong grammatically I'd appreciate any help, I want this to be flawless.