Give an example of UB code that you have committed in real life, not from blogs. I am genuinely curious.
182 karma · joined April 3, 2024
Give an example of UB code that you have committed in real life, not from blogs. I am genuinely curious.
I set DPI so that a 15pt font occupies 15pt physical space on screen. Not sure how to set DPI using fractional scaling.
I guess I have to buy a 4K monitor in future.
If you don't need to use it on Mac/Windows, use a FS like BTRFS with checksumming feature.
Don't use any FS that doesn't have checksum feature as silent bitrot is real.
I was programming in the 90s when these languages emerged. Developments environments were emacs, vi, Brief, Borland IDE, etc. There were a few other IDEs available, but about $200 per seat.
All the scripting languages mentioned didn't come as default in Unix or Windows. You had to download from their own websites.
It was mostly Visual Basic, C, COBOL that were popular.
Just taking a 500mg x 2 Vitamin C supplements should provide enough for skin repair.
You answered my question. My original argument was using concurrency primitives "properly" in C++ prevents memory issues and Rust isn't strictly necessary.
I have nothing against Rust. I will use it when they freeze the language and publish a ISO spec and multiple compilers are available.
With POSIX semaphores, mutexes, and shared pointers, it is very rare to hit upon a memory issue in modern C++.
Source: Writing code in C/C++ for 30 years.
I just unsubscribed from the digital edition. A neoliberal and globalization bias in overall tone.
On shortwave, we even have 250,000 W transmitters just blasting RF everywhere.
We call them flame throwers for a reason.
Context please? Which country and city?
I have found Asian countries, Japan and UK the same as US when it comes to customs experience.
Lack of LuaJIT for 5.1+ isn't that big of a deal for desktop apps. The embedded world is still stuck in 5.1, but for them, the benefits of the latest Lua is marginal.
Low level languages always came with a set of usage guidelines. Either you make the language safe for anyone that they can't shoot themselves in the foot and end up sacrificing performance, or provide guidelines on how to use it while retaining the ability to extract maximum performance from the hardware.
C/C++ shouldn't be approached like programming in Javascript/Python/Perl.
Give an example. I have been programming in C/C++ for close to 30 years and the places where I worked had very strict guidelines on C++ usage. We could count the number of times we shot ourselves due to the language.
Modern C++ has reduced a lot of typing through type inference, but otherwise the language is still strongly typed and essentially the same.
Have you studied Software Engineering? They discuss LOC in depth and many academic papers on KLOC are in SE literature.
You could also set a special mark on a packet for each container and then filter based on that. The Internet is surprsingly very thin on nft resources. I spent a few weeks learning how to write them. Definitely, not for the average consumer.