cmeerw

joined 2 years ago
 

There's no perhaps about the FBI and CISA getting snippy at buffer overflows. These people worry about exploits that threaten car-crash incidents in enterprise IT, and they've seen enough to get angry. It's not that making mistakes is a crime when writing code. No human endeavor worth doing is without error. It's more that this class of bug is avoidable, and has been for decades, yet it pours out of big tech like woodworm from a church pew. Enough already, they say. They are right.

[–] cmeerw@programming.dev 1 points 6 days ago (1 children)

see https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3471r2.html#enabling-hardening

Much like a freestanding implementation, the way to request a hardened implementation is left for the implementation to define. For example, similarly to -ffreestanding, we expect that most toolchains would provide a compiler flag like -fhardened, but other alternatives like a -D_LIBCPP_HARDENING_MODE= macro would also be conforming.

 

On Saturday, the ISO C++ committee completed the second-last design meeting of C++26, held in Hagenberg, Austria. There is just one meeting left before the C++26 feature set is finalized in June 2025 and draft C++26 is sent out for its international comment ballot (aka “Committee Draft” or “CD”), and C++26 is on track to be technically finalized two more meetings after that in early 2026.

 

It is now 45+ years since C++ was first conceived. As planned, it evolved to meet challenges, but many developers use C++ as if it was still the previous millennium. This is suboptimal from the perspective of ease of expressing ideas, performance, reliability, and maintainability. Here, I present the key concepts on which performant, type safe, and flexible C++ software can be built: resource management, life-time management, error-handling, modularity, and generic programming. At the end, I present ways to ensure that code is contemporary, rather than relying on outdated, unsafe, and hard-to-maintain techniques: guidelines and profiles.

[–] cmeerw@programming.dev 3 points 3 weeks ago

I wonder if it would be possible to build such a tool on top of tree-sitter (although not sure tree-sitter's C++ grammar can handle modules yet)

 

With P2900, we propose to add contract assertions to the C++ language. This proposal is in the final stages of wording review before being included in the draft Standard for C++26.

[–] cmeerw@programming.dev 9 points 1 month ago (1 children)

Isn't that mainly just torrent trackers that publish your IP address and then the ISP gets a request for who was using that particular IP address. I don't think an ISP would itself be interested in detecting whether their customers download illegal content - there is no business case for them to do that.

 

Full-text search engine for the C++ Working Draft (and older versions from Tim Song's repository)

 

On Saturday, the ISO C++ committee completed the third-last design meeting of C++26, held in Wrocław, Poland. There are just two meetings left before the C++26 feature freeze in June 2025, and C++26 is on track to be completed two more meetings after that in early 2026. Implementations are closely tracking draft C++26; GCC and Clang already support about two-thirds of C++26 features right now.

36
submitted 5 months ago* (last edited 5 months ago) by cmeerw@programming.dev to c/cpp@programming.dev
[–] cmeerw@programming.dev 15 points 7 months ago

at least you could keep their reviews so users could at least know if the app can be trusted.

You mean, don't trust a flatpak uploaded by a random person, but if there are enough fake reviews, it can be trusted?

[–] cmeerw@programming.dev 8 points 1 year ago

Also the location of known Wifi networks.

[–] cmeerw@programming.dev 10 points 1 year ago

Embracing the GC

I never actually liked the GC in D as it didn't seem to fit in with the general direction of the language, and Walter Bright in D at 20: Hits and Misses says:

Miss: Emphasis on GC

[–] cmeerw@programming.dev 1 points 1 year ago

There is also lowendspirit, but in both cases you have to be very careful what you buy - not everything that is advertised there will work as advertised or will work long-term

[–] cmeerw@programming.dev 1 points 1 year ago

where they will double your monthly data limit for free when you comment your order number.

where they use you to spam the forum thread (for giving away something rarely anyone has any use for)

[–] cmeerw@programming.dev 4 points 1 year ago (1 children)

So they actually rewrote The Hurd in Rust.

[–] cmeerw@programming.dev 3 points 1 year ago (4 children)

There is no reason to “hate” Ubuntu but there are better choices.

What are those better choices then (for those who currently use the non-LTS Ubuntu releases and don't want to move to rolling releases or LTS-only releases)?

[–] cmeerw@programming.dev 6 points 1 year ago

I still think Ubuntu is the best option (particularly if you want to use the non-LTS releases)

Having said that I do hate snaps and also dislike flatpaks. So what I do is just use the Firefox deb package from the PPA and the chromium package from Linux Mint. Oh, and I have actually replaced ubuntu-advantage-tools with a no-op dummy package.

[–] cmeerw@programming.dev 3 points 1 year ago

Only issue is they’re stored in my server as belonging to the server user (I assume everything in those directories should belong to root and I can just use chown?) But I also don’t know if they retain the same permissions when backed up.

Not everything will be owned by root, and some of the binaries will be setuid or setgid, some might even have extended attributes (e.g. ping will usually have a security.capability attribute). /var will also have a lot of different owners.

view more: next ›