What if friend in C++ wasn't for bypassing, but for locking things down?

4 points

a year ago

I’m not from CS – background is biotech – but I’ve been building a system in C++ where modules aren't allowed to touch memory or override anything unless they're explicitly granted access.

I used `friend` + `final` not as shortcuts, but to block behavior, sandbox memory, and force everything to go through one pipeline: Wrapper → Interface → Access → Pointer.

No runtime IDs, no if-checks, no const tricks – just raw C++ syntax doing the gatekeeping at compile-time.

The whole thing is kinda like gene expression. You don’t “do” something unless the system says you’re allowed to.

I’m calling it BIA – BioMorphic Instruction Architecture. It’s experimental, probably flawed, but I’d like to know: > Has anyone else tried locking down C++ this way?

GitHub repo here: https://github.com/Nomatter2021/biomorphic-instruction-architechture