15.01.2012, 03:46, "Juan Jose Garcia-Ripoll" <juanjose.garciarip...@googlemail.com>: > I am afraid this is due to ASDF: it overrides your handlers by > inserting one that breaks when the compiler signals some error or some > warning. > I find it very annoying because it makes debugging compiler errors very very > hard.
ASDF had some annoyances related to compiler warnings, but waht I experience is a different issue.I think so because I use my code to compile and load lot of libraries. Maybe on them produce compiler warnings or fail to compile at all, and my code always catches the error (even on ECL and other lisps). But sometimes ECL starts to enter debugger. What is important, it happens not always when this file is compiled, but seems to depend on what compiler did before compiling this file. I have impression something in ECL sets compiler:*compiler-break-enable* to T, which causes entering debugger. See attach for a lisp session (copy paste from console). When in debugger i chose the "try recompiling" restart, and every time the file is recompiled I again trap into the debugger. Until I set compiler:*compiler-break-enable* to NIL, After this compilation still fails, but the debugger is not entered, and my code continues as expected (i.e. handler-case catches the error) Best regards, - Anton
lisp-session.txt
Description: Binary data
------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
