2 ms·
The part that's closer to how the computer works is the part that lets you write an allocator. Witness any discussion of a pointer bug at any level of the stac
by asveikau 8y ago
The part that's closer to how the computer works is the part that lets you write an allocator.
Witness any discussion of a pointer bug at any level of the stack. No matter what the piece, someone will jump in and say, "that should have been bounds checked!" A lot of times it's true. But what they miss is that the bounds check needs to come from somewhere, which means there is a layer of the system where it doesn't apply. Somewhere you have a larger piece of memory, and it gets divided into smaller chunks, and the boundaries are fiction, meaningful only to a higher level abstraction. This is the way it needs to work.
Reducing the code in which that's a concern is likely legitimate. But then you enter into "that's not really how it works".