nice gnu errors

[bigearsbilly]

There's a filter one can apply to gnu C++ error messages.

I can't for the life of me remember what it is called,
cannot find it with google,
I know it's on my box somewhere.

anyone help?

[ne555]

What do you mean? What will the filter do?

[Disch]

It might be called "writing good code"

Writing good code will filter all error messages.

=P

[simeonz]

http://www.bdsoft.com/tools/stlfilt.html

EDIT: have never used it

[Disch]

ooooooh. That's what he meant. XD

[jsmith]

Yes, and all that does essentially is regex pattern matches for the most common compile errors, I've found. I actually don't find it that useful. (The most useful compile error is the one that points to the line of code I wrote that originally caused the compile error.)

[bigearsbilly]

stlfilt aah yes that could be it.

I find it occasionally useful, I don't use it all the time but it's helpful sometimes.
it at least cuts the length down a fair bit.

@disch unfortunately I haven't reached the point where I never get compiler errors, unlike yourself?
:p

[jsmith]

No, no, I get lots of compile errors :) Some of them several hundred lines long for a single error. I read the first line of the error and the last two (usually the real error, and the point of instantiation). Then I look at my line of code and usually it's obvious to me what the error is.

My record is something like 32 lines / 50,000 characters of output from gcc for a simple 7-line program using boost::mpl that contained two compile errors. (The whole of the source code was only about 200 characters).