> 229 If a builder builds a house for someone, and does not construct it properly, and the house which he built falls and kills its owner, then that builder shall be put to death.
> And yet, most of the time when somebody even realises they shouldn't write codecs (and file compression and various other similar technologies) in C++ their next guess is Rust which while obviously an improvement over C++ is hardly a good choice for this work either.
To me, the point of it is just to be more explicit and ease maintenance, like `typedef int meters_t`, but more extensible. Compare `int foo_len` to `meters_t foo_len`.
Explicitness: Consider the ambiguousness of `int foo_len` when you're swapping between meters and feet (but use `int` for both).
Ease maintenance: If you want to change the type you use to represent meters (say from `int` to `size_t`, since it might be wise to make it unsigned), compare going through the code and changing each meter-related instance of `int` vs. just changing the `meters_t` struct declaration.
More extensible: Compared to `typedef int meters_t`, using a struct is useful if you ever have to add to the struct. (Maybe a second numeric member representing the conversion to some other unit of length or something.)
For "meters", this doesn't really apply, but using a struct also prevents you from accidentally trying to do math with numeric types that you shouldn't do math with (like ID numbers or something): https://stackoverflow.com/a/18876104/9959012
The most amazing thing about it is how it manages to be so entertaining to read (the last thing I expected from a C++ textbook and a thing that made getting through it way easier)!
>I'm not sure if there's an even more recent edition that covers C++17 and C++20
>A thought has been lately put forward, which may or may not have truth in it. What if — instead of Jupiter being a world, inhabited by animals and people, as is often supposed, with a small distant sun and five dim moons to give them light — what if Jupiter is himself in some sort a second sun to his moons, and what if those "moons" are really inhabited planets? It may be so. That is all we can say. The idea is not an impossible one. (p. 207)
And that's still all we can say about at least one of them[0]. :)
The big green guy is the new Logitech software suite that I need to use to set the sidetone on my new headset, which asks you at install time whether you want to enable telemetry yet doesn't actually let you proceed until "yes" is checked, and which is completely redundant to yet distinct from the old suite (which new versions of the same headset model don't work with) and works less well. The other aliens are update pop-ups.
Shameless plug: I wrote a little Python timer for Linux that works great with a dropdown terminal like Yakuake: https://github.com/qiolol/timerBeetle
I often use it for timed tasks, and it's faster than reaching for my phone or even opening a browser tab (and, unlike a Google or DDG timer, it doesn't keep ringing until you re-raise the browser window, find the tab, and silence it, which always annoyed me). : p
http://faculty.collin.edu/mbailey/hammurabi%27s%20laws.htm