z_open

When the C++ standards committee make decisions crippling the language to preserve ABI (see std::regex), it's defacto part of the standard.

ok. But do they still need to scan it separately? I take contact lens fluid and I always have to wait for someone to check it before moving on.

Why does the example not show an example of unsafe C++?

I can't imagine judges would normally except this especially since it seems to be a known way to skirt law.

As they say, most people listen to their music with equipment. Audiophiles listen to their equipment with music.

What about it? It was also exposed much more publicly than this.

This is the typical interpretation.

I remember a question in English class asking what I think this could be about given the context that it was right after the war.

Most teachers were not good at checking this. There was an archive mechanism which would compress the file and IIRC, prevent it from showing up in the program list. You could of course just unarchive it.

It's funny how many software developers got into it due to being bored in class with a TI-83 and randomly trying to create programs.

I think the obvious question is are humans deterministic? A lot of inputs but it's a reasonable belief that humans are in fact deterministic.

How does it work if this is under the creative commons license? Can 3rd parties sell this controller per the model? Other 3rd party vendors got around this by making a very minor change.

I had no idea Politico was Axel Springer or that Axel Springer owned so much. The article is indeed dishonest.

Why is that NaN handling sensible? I don't think it makes sense to say log(-1) equals log(-2). Mathematically it isn't true and your implementation would say it's true only because of limitations in IEEE754.

The assign operator rebinding is yet another thing that behaves slightly different from the rest of the language.

Lots of bad advice. Using unsigned for normal integers when you know they will be positive does worse for optimization, not better. Also for (;;) {} is convention because older compilers would give warnings with while (1)

I stopped reading there.

kill Unicode. Done with this after these 25 byte single characters.

I wish I could find the pull request associated with that issue.

Tried it and realized it was gimped compared to the Linux tools it was trying to emulate. Monopolies will always be playing catchup with basic functionalities people have done for free because they make sense.

printing is never the appropriate tool. You can make your debugger print something when that line of code is reached anyway and automatically continue if you want. So what's the point of pritntf? It's just less information and features.

Not this article again. His opinions on include files don't make sense anymore. Modern compilers keep track of what includes are necessary to reprocess.

What the hell do the antitrust people in the US do? Google should have been chopped to bits a decade ago and Microsoft buying Github is just nonsense. Way too much potential for abuse all around.

They're not acting like idiots though?

And they're trying to raise awareness that Microsoft helps Israel surveil and attack Palestinians, not raise awareness that there is a war going on.

Your comment is a typical one that protests should be less disruptive, but only disruptive protests have historically been effective.

Even if we ignore solutions other languages have come up with, it's even worse that they landed on // for the syntax given that it's apparently used the same way for real comments.

> Raw or multiline strings are spelled like this:

    const still_raw =
        \\const raw =
        \\    \\Roses are red
        \\    \\  Violets are blue,
        \\    \\Sugar is sweet
        \\    \\  And so are you.
        \\    \\
        \\;
        \\
    ;

This syntax seems fairly insane to me.

I had the same issue. I went back to the calendar and it said I got 100% of the words. So I guess it's not always possible and I spent all that time trying for no reason.

Not a great answer but finish them broken. If they're just for me and/or my company, document when they fail and be done with it. If it's documented then it's not a bug

He didn't mention the worst pattern, the visitor pattern, which has extremely few use cases.

Are all major programming languages going to come from corporations in web 2.0?

printf("x = %6d\ny = %.8E\n", x, y) ;

What's the equivalent lisp?

Lisp is great until I have to do something complicated like manipulate a string or add a small feature without rewriting the entire structure of the program.

Good thing those never happen.