Most new laptops I have come across in the last couple of years will charge through USB-C. Apple laptops have been able to charge through USB-C for seven years at least.

The actual chargers have been USB-C for several years. This is only affecting the port on the phone and one end of the cable.

Of course they won't. Apple uses USB-C for their laptop computers and their iPads. They also use USB-C on the other end of their charging cable and their phone chargers. They were probably going to move to USB-C for their phones at some point soon anyway.

Haha. That's not happening.

You are angry that this guy had children? There's no reason to suppose that they will be making the same mistakes, especially as they just lost their Dad.

Citation needed. I don't think he is.

In the UK, the fire engine would be liable in this situation. They are doing something that is inherently dangerous so they have the duty of care.

What you do is say "I tried this answer (with link) and it didn't work because x, y and z happened."

The first flight of SLS sent a capsule around the far side of the Moon. All of the Saturn V missions achieved stage separation and orbit.

15% of the engines failed. Is that really an acceptable failure rate?

Yes. They're going to change it ti Urectum. Here, let me locate it for you...

Plus commuting costs and more expensive food and coffee.

But POSIX doesn't define the return value from realloc(p, 0) beyond either NULL or a pointer to an object that can be freed.

I'm not too sure about the realloc example. The man page on my Mac says

That says to me its behaviour is already aligned with the new standard and I'm not sure if it ever wasn't.

Furthermore, I don't think I've ever seen C code that uses the behaviour described by the article. The example of grep doesn't use it, it only uses the "passing in a null pointer is the same as malloc" behaviour. Also, the example stack is a bit bogus. A real implementation would never bother to realloc with less memory because you're almost certainly going to need to grow the stack again at some future time.

That's just a subset of undefined behaviour and it limits what an implementation can do. For example, the designers of a C compiler for a segmented architecture may want to trap if you try to compare two pointers in different segments but give a sane answer if you compare two pointers in the same segment.

"Undefined behaviour" means "the implementor can do whatever is convenient" and for implementors targeting a flat address space, it's convenient to return a sane value no matter where the two pointers came from. It means, for example, they can implement memmove() without copying the source block into a temporary array (to avoid corruption id the source and destination overlap).