I think it's right to disable the deferred warnings check by default, but at the same time I would recommend everyone to enable it in his lisp initialization file.
Yesterday I started to use ASDF 2.31.1 where deferred warnings are checked. And found 3 bugs in the code I am working on (like referencing a special variable removed long ago, just having an accidentally typed letter 'd' in the middle of a function code, and a typo in variable name). Bugs hasn't affected me yet because I normally do not use the system in a way where the bugs will be enabled. I am glad that compiler notices the bugs and that ASDF now can inform me about them. I am not ready to propose upgrade plan. Do to so I need to learn better what warnings may detected by this new feature, and in general learn and think more about warning handling. 02.03.2013, 23:07, "Faré" <[email protected]>: > On Sat, Mar 2, 2013 at 1:50 PM, Stelian Ionescu <[email protected]> wrote: > >> It's a very good idea. The configuration mechanism is the last big >> hurdle preventing a virtual environment for Common Lisp. I think you >> should disable deferred warnings by default and keep filing bugs, >> postponing their re-enabling for 6-12 months. > > Better late than never, I have disabled deferred warnings check by > default in 2.31.6. > > I will think of a better upgrade plan before I try to push that change again. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > "I'm not a procrastinator, I'm temporally challenged" > > _______________________________________________ > asdf-devel mailing list > [email protected] > http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel _______________________________________________ asdf-devel mailing list [email protected] http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
