Closed dkochmanski closed 5 years ago
It is not clear whenever ECL screwed up on speed3/safety0 or it is bad declaration. ECL produces very unsafe code on these settings. I've spend some time to debug it but without tangilbe results. I've updated commit message.
commit message is fixed again and issue has been created.
No production system should declare safety to 0 (especially clx which has a lot of macros which are error-prone). Safety level 0 actually broke McCLIM's event processing queue on ECL.