Take a look at all the struct definition. It’s a pure virtual method of 🍽️ with a bunch of overrides in the structs that inherit from 🍽️.
Take a look at all the struct definition. It’s a pure virtual method of 🍽️ with a bunch of overrides in the structs that inherit from 🍽️.
Yeah, there really should be some expectation of stewardship in exchange for absurd post-Disney copyright durations.
Actually I would like to read that. Might be worth the risk?
You’re coming dangerously close to setting Rufus free. I have a feeling you’re about to be visited by a time traveler with a dire warning if you keep trying this.
The code is speaking to me, but it’s just word salad.
I think you mean “$EDITOR”. Gotta have that variable expansion.
Am I being dense? I don’t get it.
Unix -> Linux -> Ferrix?
I don’t understand any of these analogies at all
For practical purposes, it’s probably good enough. You could write a program to check whether it’s non-repeating up to N digits, so just set N high enough that it will last you for a few thousand releases…
I learned MIPS as an undergrad. Pretty neat little RISC architecture.
I have a similar story. I started a new job and inherited a ball of mud written in Python while the creator was out for a few weeks. When he got back, he was grumpy about my changes. I guess he preferred it with more bugs 🤷♂️
Get out of my office
I mean technically I could write an interpreter that assigns semantics to HTML constructs.
Aha, I didn’t realize compromising availability was sufficient for the CVE definition of security vulnerability. Projects I’ve worked on have typically excluded availability, though that may not be the norm.
And I see your point about some exploits being highly asymmetric in the attacker’s favor, compared to classic [D]DoS.
The chances of the coin flip yielding heads are roughly 50%, if coins don’t not exist.
Maybe I’m misunderstanding you, but DoS is exactly the same thing as “denial of service”.
My point is that memory leaks can only degrade availability; they are categorically distinct from security vulnerabilities.
I had to look it up to check my memory. Yup! https://about.gitlab.com/blog/2015/06/05/how-gitlab-uses-unicorn-and-unicorn-worker-killer/
I don’t think memory leaks could ever amount to a security vulnerability, but it just feels yucky. I guess I shouldn’t cast stones, I write C++ at work.
Git kinda has it? Have you seen git notes? https://git-scm.com/docs/git-notes
Imagine if you could block notifications matching a regex