That’s not always good. Maybe they just did not read the handle and assumed someone random asked, but didn’t know they wanted this library. That’s probably a good assumption, too.

Ok, but what did they try to do as a SaaS?

Yes. Unless you have a really good reasons there are safe and portable versions you should use instead.

If you tell the Compiler to be careful and avoid writing c code c++ does not segfault. This is a user error.

You can technically even write Assembler code and compile with gpp.

You are a complete idiot, it’s objectively hard to find.

That’s only due to technical reasons on weird platforms like x86, 64bit x86 or ARM.

The checkbox should be grayed out.

You might want to consider used hardware. Should be ca. 50 Bucks+ drives.

Used drives are quite cheap, too. Just use some redundant setup.

And you should.

It even works for classes whose constructors your implementation cannot see, if you aren’t a bitch about it.

In C++ you should never have owning raw pointers. Unless you have a good reason™.

Raw pointers are great, but not for ownership.

Because stuff can own other stuff and be owned at the same time. Also, arcane jackarsery.

Edit: if you want to give a function a pointer that it may change this may occur in a constructive way. I.e. replace an owned object.

That’s unreasonable mate. Rebar is good and compute has always been cheaper if you stack more of it, to a point.

A compatible mono is dirt cheap anyway. Stop wasting electricity by running very legacy systems.

That’s why they need 55 years of experience. They are trying to hire the original dev.

Issue here is that this is very hard to Do. Gotta get paid for that level if software.