Slashdot Mirror

← Back to Stories (view on slashdot.org)

Bjarne Stroustrup Announces the C++ Core Guidelines

Posted by timothy on from the never-quite-reaches-b-minus dept.

alphabetsoup writes: At CppCon this year, Bjarne Stroustrup announced the C++ Core Guidelines. The guidelines are designed to help programmers write safe-by-default C++ with no run-time overhead. Compilers will statically check the code to ensure no violations. A library is available now, with a static checking tool to follow in October.

Here is the video of the talk, and here are the slides.The guidelines themselves are here.

4 of 262 comments (clear)

  1. Wait what? by Virtucon · · Score: 4, Funny

    If you take all the fun out of finding memory leaks and stack overflows what fun is there to C/C++? I mean I just love using AutoPtr everywhere, it's perfect!

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
    1. Re:Wait what? by Pseudonymous+Powers · · Score: 5, Funny

      Everything in C++ is now deprecated except the word "safe". So you should really be using safesafe::safe_safe_safe in such situations. And in all other situations. When in doubt, just keep typing "safe" until it's safe.

  2. Re:Effort will help by Anonymous Coward · · Score: 0, Funny

    Sounds like you're a nincompoop with an MBA who cares more about name dropping and buzzword bingo than you do about code. Pro tip: nobody takes an anonymous coward seriously when they claim to be an "expert". Trust me. I am an expert at detecting no-nothing management boneheads.

  3. Re:Frist! by Anonymous Coward · · Score: 3, Funny

    "print" is deprecated. You must now use the safe_print_n function and get a safe pointer back using the SafetyFirst() method of the SafeLiteral class.

    Because safe by default, amirite?