News for hackers. Stuff that matters.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by astrange on Wednesday April 20, 2022 @06:48PM (#31104064)
Apple platforms used to have that ("zero-link") and removed it quickly because nobody actually liked it. I think this and Lisp/Smalltalk's image model is actually mistaken.

It goes against the principle of "crash-only recovery" to try to recover from a bad state instead of being able to start over from the beginning.

Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Wednesday April 20, 2022 @07:17PM (#31104307)
Generally in CL you should be able to recover from a usable intermediate state and restart from there.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by astrange on Thursday April 21, 2022 @08:34PM (#31116882)
That encourages you to live off the intermediate image forever (like autogenerating code and then not maintaining the source for it), but if you miss some data corruption then you're stuck with it.
Re:IKOS: Static analyzer for C/C++ based on the theory of Ab... by jhgb on Friday April 22, 2022 @09:31AM (#31121333)
You already are autogenerating code in Lisp (using macros), but not without keeping the source for it, which still lives in the source files. If those files are not loadable into a clean image, you're doing something wrong (like CMUCL people find out a long time ago).