C++ Tips of the Week

by fauigerzigerk • 9 years ago

212 34 9 years ago

signa112• 9 years ago

something similar was initiated by herb-sutter as well in his 'guru of the week' (gotw) columns. which then became books in their own right aka 'exceptional c++' series.

are these tips more 'modernish' ?

fauigerzigerk• 9 years ago

Both series have been created over many years, so I'm not sure which one is more modern. Herb Sutter says that all GotW articles are being revised to reflect changes in C++14.

SwellJoe• 9 years ago

Tip #1 covers a feature found in C++17, so I'd say yes.

jzwinck• 9 years ago

Tip #1 appears on the surface to be about C++17's std::string_view, but many shops had something similar to string_view for a decade or more before C++ made it official. The tips are not presented in their original form; edits have been made (as per the linked page). I think Google had something like string_view by 2009 at the latest, using C++03 compilers.

stochastic_monk• 9 years ago

Herb Sutter's recent tips are more modern (and the backlog is being updated).

Scott Meyers' Effective Modern C++ is a great successor to his Effective C++ book which spawned the whole "Effective *" snowclone books and covers C++14, though not 17, of course.

Actually, this blog post's content looks like a watered-down version of a tip from either or both of the above authors, though I'm too lazy to chase down a verification.

branchless2• 9 years ago

I've failed the first test: how do I get a list of all "tips"?

ma2rten• 9 years ago

I think they only made those 4 public for now.

branchless2• 9 years ago

shame, was going to binge read them

unkown-unknowns• 9 years ago

Seems that only four of the tips are available?

bpicolo• 9 years ago

They're doing one a week, starting 4 weeks ago.

dogruck2• 9 years ago

They should reindex their archive of tips. I was baffled by the jump from tip 1 to 55 to 77.

Edit: the indexing is explained in a note on the site.

misnome2• 9 years ago

On average it seems, because it took a months wait for three to be released at once.

Hopefully whatever stopped the project has been resolved and they’ll be consistent now.

ThePhysicist• 9 years ago

In a similar vein, we published a „little book of Python anti patterns“ a while back, maybe some people find it useful:

https://docs.quantifiedcode.com/python-anti-patterns

ndh22• 9 years ago

We’ve decided to expose most of these tips to the Abseil development community, and the C++ community at large. Over the coming months, we’ll be posting new tips as we review and refine them for publication. Not all the entries we’ve written are relevant to the outside world; some were specific to our internal tools and abstractions, and some have become obsolete as the language has changed.

xarball• 9 years ago

I followed a few links to Abseil:

Consisting of the foundational C++ and Python code at Google, Abseil includes libraries that will grow to underpin other Google-backed open source projects like gRPC, Protobuf and TensorFlow.

This library already seems like it is suffering from scope-creep. Tensorflow, gRPC, and Protobuf are hardly related to improving the C++ standard. Why are these even in the same library at all?

ndh22• 9 years ago

They're not. They will be using Abseil.

misnome2• 9 years ago

“Underpin” e.g. those libraries will use Abseil as a common base.

perfmode• 9 years ago

Google needs to open source its core C++ libraries if it is going to open source the projects that depend on the core libraries.

HellDunkel• 9 years ago

Here is my personal advice: whatever code you write, make sure you can grab it and run leaving no trace behind.

deepakkarki• 9 years ago

For those interested in such insightful tech reads, I run https://discoverdev.io - a daily curated list of top 8 to 10 engineering blog posts!

Published every weekday!

hartcw• 9 years ago

Naming of the title reminds me of the best C book I've read, "Expert C Programming: Deep C Secret" by Peter Van Der Linden.

https://g.co/kgs/Gyvg69

mbrubeck• 9 years ago

Use string_view, but beware of use-after-free bugs like https://github.com/isocpp/CppCoreGuidelines/issues/1038

inetknght• 9 years ago

Think of string_view as a non-owning pointer to a known-size array. If the array is moved or destroyed, then string_view is left dangling... just like a pointer.

C++ Tips of the Week

Related Stories