2 ms·
I agree that you can usefully, formally specify certain behaviors by choosing to ignore, e.g., implementation details. There are a lot of implementation details
by ncmncm 7y ago
I agree that you can usefully, formally specify certain behaviors by choosing to ignore, e.g., implementation details. There are a lot of implementation details: stack depth, instruction mix, power consumption, timing fluctuation, memory placement. Incorporate too many, and you lose clarity, even usability.
But implementation details are often what hackers rely on.
So, yes, formal modeling is useful, sometimes essential, but does not eliminate hackability. Overselling it does harm.