in reply to Re: A faster?, safer, user transparent, shared variable "locking" mechanism.
in thread A faster?, safer, user transparent, shared variable "locking" mechanism.

If shared SV*s ( and all things pointed at from them ) are allocated in the protected memory, then any write access, including those done by the system as the result of apparently read-only user code, would also trigger the exception and so be protected.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^2: A faster?, safer, user transparent, shared variable "locking" mechanism.
  • Download Code

In Section Meditations