<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://www.sandordargo.com/</id><title>Sandor Dargo's Blog</title><subtitle>Sandor Dargo writes about about C++, software development, books and stoic philosophy applied to software craftsmanship</subtitle> <updated>2026-07-08T07:05:32+02:00</updated> <author> <name>Sandor Dargo</name> <uri>https://www.sandordargo.com/</uri> </author><link rel="self" type="application/atom+xml" href="https://www.sandordargo.com/feed.xml"/><link rel="alternate" type="text/html" hreflang="en-US" href="https://www.sandordargo.com/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Sandor Dargo </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Propagating exceptions from destructors with std::exception_ptr</title><link href="https://www.sandordargo.com/blog/2026/07/08/exception_ptr" rel="alternate" type="text/html" title="Propagating exceptions from destructors with std::exception_ptr" /><published>2026-07-08T00:00:00+02:00</published> <updated>2026-07-08T00:00:00+02:00</updated> <id>https://www.sandordargo.com/blog/2026/07/08/exception_ptr</id> <content src="https://www.sandordargo.com/blog/2026/07/08/exception_ptr" /> <author> <name>Sandor Dargo</name> </author> <category term="dev" /> <summary> A few weeks ago, I wrote about what happens when a destructor actually throws and why it is a dangerous idea. One of the readers commented that he was once in a situation where he had to propagate an exception from a destructor. But as a destructor cannot safely throw and it also cannot return any value, he needed a better solution. And that solution was std::exception_ptr. Let’s look into wh... </summary> </entry> <entry><title>C++26: constexpr virtual inheritance</title><link href="https://www.sandordargo.com/blog/2026/07/01/cpp26-constexpr-virtual-inheritance" rel="alternate" type="text/html" title="C++26: constexpr virtual inheritance" /><published>2026-07-01T00:00:00+02:00</published> <updated>2026-07-01T19:45:15+02:00</updated> <id>https://www.sandordargo.com/blog/2026/07/01/cpp26-constexpr-virtual-inheritance</id> <content src="https://www.sandordargo.com/blog/2026/07/01/cpp26-constexpr-virtual-inheritance" /> <author> <name>Sandor Dargo</name> </author> <category term="dev" /> <summary> constexpr has come a long way since its introduction in C++11. Back then, constexpr functions were extremely restricted and could essentially contain only a single return statement. C++14 relaxed those restrictions, allowing local variables, loops, and multiple statements. C++20 was another major milestone, bringing support for constexpr dynamic allocation, enabling types such as std::string an... </summary> </entry> <entry><title>Trip report: ACCU On Sea 2026</title><link href="https://www.sandordargo.com/blog/2026/06/24/trip-report-accu-on-sea-2026" rel="alternate" type="text/html" title="Trip report: ACCU On Sea 2026" /><published>2026-06-24T00:00:00+02:00</published> <updated>2026-06-24T00:00:00+02:00</updated> <id>https://www.sandordargo.com/blog/2026/06/24/trip-report-accu-on-sea-2026</id> <content src="https://www.sandordargo.com/blog/2026/06/24/trip-report-accu-on-sea-2026" /> <author> <name>Sandor Dargo</name> </author> <category term="books" /> <summary> Once again, I got the chance to come to Folkestone, UK. I think this was my fifth time, but the first one at ACCU On Sea. Yes, there is no more C++ On Sea, there is no more ACCU in Bristol — they got merged into ACCU On Sea. The venue is the same as C++ On Sea, many organisers are the same, but of course there are also changes. The conference chair is no longer Phil Nash but Guy Davidson. Th... </summary> </entry> <entry><title>Memory Management in C++ by Patrice Roy</title><link href="https://www.sandordargo.com/blog/2026/06/17/memory-managenent-by-patrice-roy" rel="alternate" type="text/html" title="Memory Management in C++ by Patrice Roy" /><published>2026-06-17T00:00:00+02:00</published> <updated>2026-06-29T22:42:14+02:00</updated> <id>https://www.sandordargo.com/blog/2026/06/17/memory-managenent-by-patrice-roy</id> <content src="https://www.sandordargo.com/blog/2026/06/17/memory-managenent-by-patrice-roy" /> <author> <name>Sandor Dargo</name> </author> <category term="books" /> <summary> Memory management is one of those topics that every C++ developer has to deal with, yet very few of us take the time to study it systematically. Memory Management in C++ by Patrice Roy is a book that finally gives this fundamental topic the deep and up-to-date treatment it deserves. It covers everything from the basics of how objects live in memory to modern techniques introduced as recently as... </summary> </entry> <entry><title>C++26: Cleaning up string literals</title><link href="https://www.sandordargo.com/blog/2026/06/10/cpp26-string-literals-cleaned-up" rel="alternate" type="text/html" title="C++26: Cleaning up string literals" /><published>2026-06-10T00:00:00+02:00</published> <updated>2026-06-29T22:42:14+02:00</updated> <id>https://www.sandordargo.com/blog/2026/06/10/cpp26-string-literals-cleaned-up</id> <content src="https://www.sandordargo.com/blog/2026/06/10/cpp26-string-literals-cleaned-up" /> <author> <name>Sandor Dargo</name> </author> <category term="dev" /> <summary> The two papers we are covering today are complementary in a philosophical sense. They both improve how string literals are handled in C++26. P2361R6 tackles strings that are never evaluated — the ones that only exist at compile time. P1854R4 tackles evaluated string literals, making non-encodable characters ill-formed instead of implementation-defined. Let’s start with the unevaluated side. ... </summary> </entry> </feed>
