
Sign up to save your podcasts
Or


This week we chat with a vector-of-bool (a.k.a. Colby Pike).
We talk about pseudonyms, modules, build systems and his standard layout proposal, Pitchfork.
But what prompts Michael Caisse, in the chat, to respond, "because we are not monsters",
Links:
This week we chat with a Yuri Minaev, of PVS Studio, about static analysis - and why you shouldn't be skipping on this essential part of software development.
Why is using a static analysis tool better than peer review (the clue is in the title)? Should you do both?
We also discuss the billion dollar mistake and the perils of copy & paste (and how you can mitigate them).
All in all, a step towards safer coding.
Links:
This week we chat with a panel of C++ trainers from around the world (but mostly from Germany, for some reason) - Nicolai Josuttis, Jason Turner, Rainer Grimm, Klaus Iglberger and Mateusz Pusz.
We talk about how bringing in a good trainer will keep your costs down, whether online training works or not, and why C++ is different to most other languages when it comes to training.
One of our guests reveals that he has had, and has recovered from, COVID-19 - but who?
Links:
This week we chat with Bryce Adelstein Lelbach about how the ISO C++ WG21 committee is evolving - and his roles within it (and beyond) are evolving, too.
We also look at the cross-over and interaction with the C standard, and even other languages. Is C really the Latin of programming languages? What is the relationship between the languages and the committees at this point? And why did so many committee members agree to a plan that contains items they may not be interested in?
And what happened to the Varna meeting, anyway?
Links:
This week we chat with five members of the SG16 Unicode Study Group, Zach Laine, Tom Honermann, Steve Downey, Peter Brett and Corentin Jabot.
We talk about their efforts to get all things Unicode into the C++ standard in a tour that takes us from 5000 years ago, through the 80s and 90s up to the 2020s! We look at every known language, including a few dead ones - and some that are purely fictional.
Do you know the difference between a code unit and code point? A glyph and a grapheme cluster? String a Text? And what's wrong with Locales anyway?
This show sorts it all out.
Links:
This week we chat with James Berrow about colo(u)r, and how we're doing it all wrong (and not just the spelling).
We look at why colour management is complicated, how RGB doesn't exist, and how everybody (well, almost everybody) gets it all wrong.
Links:
This week we chat with JeanHeyd Meneide (A.K.A. ThePhD) about coming full circle on std::embed, as well as whether optional references should rebind or assign-through.
Packed with edge-of-the-seat stories of interesting proposals adventures through the standardisation process, as well as a decent amount of ranting.
Links:
This week we chat with Ansel Sermersheim and Barbara Geller about Copperspice, Doxypress, csLibGuarded and kitchen utensils.
We find out that Barbara and Ansel are not just library people but are actually programmers - and programmers that know how to build abstractions.
We chat about why they started CopperSpice, how it got it's name, and what else they've been working on.
Links:
This week we chat with Greg Law about debugging and going back in time!
How do things change when we can wait for something to go wrong, then go back to any point in time and examine the program state, like The Matrix's "Bullet Time"? How is this even possible, and what challenges need to be overcome? We also answer that age old question: what's the first thing people ask for when you say you can give them a time machine?
Links:
This week we chat with Vittorio Romeo about the pros and cons of backwards compatibility in C++, and his proposal to get the best of both worlds: Epochs.
As well as language compatibility, we also discuss ABI compatibility - why breaking these things is such a problem, but how not breaking them is increasingly becoming a problem.
We also, finally, get an answer to the age of question of, "how many programmers does it take to change a lightbulb?"
Links:
From the publisher's feed