Viewing profile — legalcorrection

I'm sure. It's really a lovely place full of lovely people. And the standard of living is still relatively high. They are their own worst enemies sadly.

> sigh what is the point. Might as well talk gibberish in this "us vs them" society Yeah it’s too bad. The quality of service has totally gone to shit in this country. But God forb…

Incredible to see how many people in these comments are mad that someone dare challenge that their dear GNU/Linux is a great desktop OS. This is part of why it will never get there…

In your world, disease and famine would be much more common than they are now.

It’s a false promise. You’re just moving the complexity elsewhere, into wiring this ridiculous graphql infrastructure together and making it actually do what you want in all but th…

Ignore all the noise and just use an RPC model between your backend and frontend. All these stupid trends and overengineered abstractions will come and go, but people will still be…

MSVC doesn’t enforce strict aliasing to begin with. And passing /d2UndefIntOverflow makes signed integer overflow well-defined. Even if you don’t pass it, MSVC is very conservative…

Okay so take the two most complained about UBs, improper aliasing and signed integer overflow. Every compiler I’ve ever used lets you turn both into defined behavior.

Oh really? Then why does every compiler I use have a parameter to turn off strict aliasing? You cite to a source that contradicts you. In the llvm blog post: "It is also worth poin…

Your comment is indecipherable. It sounds like it might be interesting. Any chance you could rephrase?

It’s not the greatest but it’s also not awful. Ideally the 123 would be replaced by a less common sequence, and maybe add one more word, but as is, it’s fine .

These people are just regurgitating HN memes and then flailing when someone prods a bit deeper. C is basically the Donald Trump of HN. All rational thought goes out the door at the…

Tell me, what’s wrong with variably modified types specifically?

You are confusing the C standard and actual platforms/C implementations. A lot of things are UB in the standard but perfectly well defined on your platform. Standards don’t compile…

You are entering the function. It's not in the function body in the source file, but the code is almost certainly inserted at the beginning of the function in the compiled output.

This is a common misconception. Cold emailing is legal under the CAN-SPAM Act.