Dynamic_cast(C)++

teamten.com

44 points·jlangenauer··14 comments

Don't forget Bjarne Stroustrup's http://docs.google.com/viewer?a=v&q=cache:JyMHnEtpuZgJ:t... Generalizing Overloading for C++2000. We'd all be a lot better off if we'd just listened back then.

He does a good job of making the justifications for each feature almost plausible. Whitespace as operator overloading for physicists who want to write "x y" to mean "x times y." Sure, why not?

operator (....) {} :p

Someone, somewhere will read this and use it as a basis for upcoming interview question answers. Now my job is more complicated by the fact that I have to separate the gullible from the ignorant. Thanks...

Early April fools?

To reflect the enhancements to the language since 1983, the name of the language has been changed to: dynamic_cast<std::integer>(C)++.

I would think so.

MyClass ptr = new MyClass;

MyClass ptr = old MyClass;

This one made my day :D

You knew the pedantry was going to come.

The title is invalid syntax. Or at least I'm pretty sure it is unless you have a function or class named Dynamic_cast. I hate C++.

It is - HN stripped out the template name from the title.

Looks frighteningly real in a few places.

Maybe there's a C++ equivalent for Poe's law where real C++ extension drafts are indistinguishable from parodies.

I love point #2: all local variables must be explicitly freed. Truly raises the bar on breaking backwards compatibility :)

Hey, given how the price of memory has fallen I would consider that sufficiently backward compatible.

Data doesn't need to be deleted these days. not even in RAM!

shared_ptr & weak_ptr are way cooler

Reply on news.ycombinator.com