3 ms·
Wow, you're daft. Everything is, ultimately, getting turned into machine code. Not even Lisp Machines could get away from this fundamental fact: http://funcal
by aryastark 13y ago
Wow, you're daft. Everything is, ultimately, getting turned into machine code. Not even Lisp Machines could get away from this fundamental fact: http://funcall.blogspot.com/2009/04/some-lisp-machine-minutia.html http://funcall.blogspot.com/2009/04/some-lisp-machine-minuti...
> Bogus objects — properly tagged words with invalid addresses that pointed at uninitialized memory or into the middle of object of a different type — which would cause the GC to corrupt memory would be left in registers or on the stack. These sort of problems were everywhere in the microcode.
Go build your cabin in the woods now.
- lispm 13y agoSure one can corrupt memory on a Lisp Machine. System software like the micro code or the garbage collector can contain bugs. Something like a buffer overflow was very very rare. This was not a systemic problem like it is in C.