Re: with-compilation-unit

Attila Lendvai wrote:
> dear list,
> asdf's OPERATE is wrapping basically everything in a bigWITH-COMPILATION-UNIT, even TEST-OP's.
> on sbcl it locks the *big-compiler-lock* which basically stops allother threads and because of that i can't start the UCW tests from the'test-op... removing the w-c-u solves this problem.
> i suspect that it accumulates the compiler warnings/errors, but whatelse does it do?
> any chance of removing it?
> or is it sbcl's fault that it locks that big lock?
> any ideas/suggestions?
> -- - attila

I think that we really need it; without it we will get floods of 
spurious undefined function warnings.  Now, it might be possible to be 
more refined about the scope of the with-compilation-unit so that, for 
example, it doesn't wrap a test-op.

Do you need multi-threading in anything other than the test-op?  It 
seems kinda weird to want multi-threading in the compilation process..

> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV