"There is no cannibalism in the British navy, absolutely none, and when I say none, I mean there _is_ a certain amount."
Readit NewsDeleted Comment
eternal_july commented on Facts about migration and crime in Sweden government.se/articles/20... · Posted by u/teddyh
eternal_july commented on Const and Optimization in C nullprogram.com/blog/2016... · Posted by u/adamnemecek
you skipped the first clause of my sentence --
if a variable is declared const, casting away const-ness is undefined
is that not true?
To reinforce the sibling comment's point:
A very common pattern is when a const variable resides in non-writable memory (happens all the time in embedded), - if you attempt to write to it, you trigger a fault.
So if you cast away constness to conform to some API and then read the value, everything is fine (aside from questionable API design, of course). Modifying the value is another story, though.
eternal_july commented on Practical Guide to Bare Metal C++ arobenko.gitbooks.io/bare... · Posted by u/adamnemecek
He's talking about real time code here and completely missing one of the main reasons why you have to use great care using C++, and even parts of the C libraries ... all those hidden mutexes in new/malloc and other parts of the standard libraries (stdio too)
I'm sure we all know what happens when your ISR quietly does a new while some other part of your code is holding one of the locks deep in malloc.
But far more important is avoiding priority inversions when a low priority thread is holding a lock in a library somewhere, they result in high priority threads missing real-time deadlines - the sort of heisenbugs that are pretty impossible to find .... and are best to avoid by design.
> I'm sure we all know what happens when your ISR quietly does a new while some other part of your code is holding one of the locks deep in malloc.
Yeah, what happens is that such code does not pass code review :)
In 99.99% of cases an ISR should only set some flag, that is then checked by code, running in user mode (or whatever it is called for your platform). Then the real work is done in user mode. The remaining 0.01% of cases does not involve using dynamic memory either.
It still seems to me that Linux should follow FreeBSD and not mount it as a filesystem and just use a library to manipulate the values. It clearly has some huge problems with being a filesystem. This isn't Plan 9 and everything does not have to be a file.
Of course everything doesn't have to be a file (it is only that way on Unices). On Linux everything is a filesystem!
I was semi-hoping, that "résumé validation" would validate it against things like expected buzzword frequency, HR stopwords and so on. The important things, you know.
I'm confident that self-driving cars will eventually be safer than human driven ones. I'm not confident that this can be realistically achieved without killing some unfortunate bystanders in the process of getting to that point. That doesn't mean we should accept these cars running amok killing people all over the place. It doesn't mean I think this specific case involving Uber is "reasonable" either. I just think, in a general sense, a realist has to be able to try to find some balance between short term lives lost and long term lives saved.
Perhaps, it is easier to speak of things like "short term life lost vs long term life's saved", as long as it is other people losing lives.