When trying to set up the audacity project <http://wiki.audacityteam.org/index.php?title=Developing_On_Windows>, I encounter a lot of problems, especially with parsing. P.e. when changing the include paths for a project. Both minGW and Cygwin. Sometimes deadlock, often stopping at 100%. It is certainly not my system resources (8-core, i7-960), as only 12% CPU is used during this parsing. Now this seems to have influenced also my Java projects, for parsing errors are given without having changed the code, while it also compiles normally. My suggestion would be that developers would use audacity as a test case for the C++ module.