<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://izaron.github.io/</id><title>C++95</title><subtitle>Izaron's C++ blog</subtitle> <updated>2024-05-09T18:48:58+00:00</updated> <author> <name>Evgeny Shulgin</name> <uri>https://izaron.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://izaron.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://izaron.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.3.2">Jekyll</generator> <rights> © 2024 Evgeny Shulgin </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>char, but not char 🤔</title><link href="https://izaron.github.io/posts/multichar/" rel="alternate" type="text/html" title="char, but not char 🤔" /><published>2023-02-12T11:00:00+00:00</published> <updated>2023-02-12T11:00:00+00:00</updated> <id>https://izaron.github.io/posts/multichar/</id> <content src="https://izaron.github.io/posts/multichar/" /> <author> <name>Evgeny Shulgin</name> </author> <category term="Article" /> <summary> When you explore a file format, you may find file signatures. A file signature is a sequence of bytes that used to verify the content of a file. A file signature may look as a sequence of “magic bytes” (unique for this type) at the beginning of a file. There is a list of file signatures for some formats on wikipedia. Bytes at the beginning of the file are often human-readable, meaning that the... </summary> </entry> <entry><title>Exceptions in C++ and Garbage Collection - what do they have in common? ♻️</title><link href="https://izaron.github.io/posts/exceptions-gc/" rel="alternate" type="text/html" title="Exceptions in C++ and Garbage Collection - what do they have in common? ♻️" /><published>2023-01-26T11:59:00+00:00</published> <updated>2023-02-10T00:59:16+00:00</updated> <id>https://izaron.github.io/posts/exceptions-gc/</id> <content src="https://izaron.github.io/posts/exceptions-gc/" /> <author> <name>Evgeny Shulgin</name> </author> <category term="Article" /> <summary> I do not mean technical similarity, but the very principle of having a feature of this sort. Initially, the feature looks cool and can be used seamlessly “out of the box”. But when there is a need to fix something in this feature, the programmer will be tortured, digging into the technical implementation of the feature. 🔍 For example, in Java (and other languages with garbage collection), it ... </summary> </entry> <entry><title>Entry threshold for contributing to compilers</title><link href="https://izaron.github.io/posts/clang-contrib-threshold/" rel="alternate" type="text/html" title="Entry threshold for contributing to compilers" /><published>2023-01-24T19:15:00+00:00</published> <updated>2023-02-10T00:59:16+00:00</updated> <id>https://izaron.github.io/posts/clang-contrib-threshold/</id> <content src="https://izaron.github.io/posts/clang-contrib-threshold/" /> <author> <name>Evgeny Shulgin</name> </author> <category term="Article" /> <summary> Once in a C++ chat, a guy asked whether it make sense to investigate and send bugfixes to existing compilers? There definitely must be a lot of people who want to fix bugs, and the issues just disappear instantly, he thought 😱 In fact, the situation with Clang/LLVM (and with many other projects) is the opposite. There are thousands of issues that no one fixes for years. The review process is ... </summary> </entry> <entry><title>The most vexing C++ rule for modular projects (and how to deal with it)</title><link href="https://izaron.github.io/posts/most-vexing-modular/" rel="alternate" type="text/html" title="The most vexing C++ rule for modular projects (and how to deal with it)" /><published>2023-01-06T11:54:00+00:00</published> <updated>2023-02-10T00:59:16+00:00</updated> <id>https://izaron.github.io/posts/most-vexing-modular/</id> <content src="https://izaron.github.io/posts/most-vexing-modular/" /> <author> <name>Evgeny Shulgin</name> </author> <category term="Article" /> <summary> While developing my pet project, I encountered what I call the most vexing C++ rule in my experience, at least for modular programs. It is linker-specific and requires sort of secret knowledge to deal with it. In large modular projects, often each business logic module corresponds to a single static library. If some module is not linked to the executable binary file (via a flag of the build s... </summary> </entry> <entry><title>The simplest std::function explanation in 15 minutes</title><link href="https://izaron.github.io/posts/std-function/" rel="alternate" type="text/html" title="The simplest std::function explanation in 15 minutes" /><published>2023-01-01T19:15:00+00:00</published> <updated>2023-02-10T00:59:16+00:00</updated> <id>https://izaron.github.io/posts/std-function/</id> <content src="https://izaron.github.io/posts/std-function/" /> <author> <name>Evgeny Shulgin</name> </author> <category term="Article" /> <summary> This post was written under influence of a cool video from Jason Turner “A simplified implementation of std::function” Often people don’t think about how std::function works. Most people know that this thing is a wrapper over something that can be “called” as a function. Some people vaguely remember that std::function somehow mess with memory on the heap. The cppreference does not reveal muc... </summary> </entry> </feed>
