Timeline for Memory isolation autochecker
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2020 at 23:24 | vote | accept | Daniel | ||
| Dec 9, 2020 at 20:12 | comment | added | Leonid Shifrin | @Daniel Glad you found it helpful. Thanks for the accept. Keep in mind the caveats I mentioned - there may be cases the current code will miss (probably not hard to account for them though - if you come across any, ping me here in comments and I will try to address them). | |
| Dec 9, 2020 at 19:39 | vote | accept | Daniel | ||
| Dec 10, 2020 at 23:24 | |||||
| Dec 9, 2020 at 19:39 | comment | added | Daniel | Oh thanks! This is incredible, and so easy to use. It even works on my nested Dynamic Modules | |
| Dec 9, 2020 at 15:19 | comment | added | Leonid Shifrin | @Daniel Well, one can use this code also without deep understanding of the internals. If you execute is, then when you call setBoundVarChecks[], this turns on the "debug" mode where all assignments to / mutations of non-localized variables inside Module or DynamicModule will issue a message. To return back to normal code execution regime, just call unsetBoundVarChecks []. That's basically it, on the "user" level. | |
| Dec 9, 2020 at 6:33 | comment | added | Daniel | I'm afraid I am having an incredibly difficult time understanding this, but I greatly appreciate it. I think I may be able to make some use of this given enough time. | |
| Dec 8, 2020 at 17:35 | history | answered | Leonid Shifrin | CC BY-SA 4.0 |