on Fri Nov 25 2011, Joel de Guzman <joel-AT-boost-consulting.com> wrote:
On 11/25/2011 11:38 PM, Roland Bock wrote:
On 11/25/2011 03:04 AM, Maxim Yanchenko wrote:
Joel de Guzman <joel <at> boost-consulting.com> writes:
Now. What else can we do about it? Here's an idea. I'd like to hear yours.
It might be good to present that in a GUI where the types are collapsed by default. Qualifications in a trace can also be optionally collapsed. Hi Joel, it's a very correct idea. In our team, I made a perl script that cleans out all compiler noise (GCC) and has some special handling for common cases like MPL_ASSERT, CONCEPT_CHECK etc. This runs for years already and proven to be extremely effective in nailing down errors. This sounds very interesting indeed. It would be cool to use it like ccache, i.e.
tmpMessageFilter -> ccache -> g++
I'm very interested. How can we get ahold of this? G++ is a good start. I'd love to see something for the "other" popular compiler as well ;-) Such a tool will be invaluable in fighting the deluge of error messages.
I presume you know of stlfilt <http://bdsoft.com>?
Ideally, I'd love to see the presentation dynamically, like in my original idea where users can click to expand the errors at any given point in the trace. Perhaps this is a good GSoC project.
I've often thought about combining the filtering tricks of stlfilt with a folding error browser. Hmm... folding errors in Emacs sounds like an amazingly good idea. -- Dave Abrahams BoostPro Computing http://www.boostpro.com