Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What I need, moreso than this, is a tool for parsing really long and winding multi-screen error messages involving templates (screw up a std::map key or value? At least 100 characters in the error message just to describe it. Add an additional 50 if you try to use string [basic_string ...])


Which compiler are you using? Clang is much better at dumping template related error messages and recent versions of gcc are getting better.


gcc 4.2, although at this stage I'm so used to reading the error messages that I just gloss over most of the verbiage


For that I use gccfilter which does an awesome job at parsing the hell out of compile errors.

http://www.mixtion.org/gccfilter/

In our project we use gccfilter with the options -c and -p which are colorize and remove path but it supports as well -a for removing the template arguments. Give it a try it will definitely help your.


Played with it, helps with some template issues involving STL, but doesn't seem to interpret CRTP (https://en.wikipedia.org/wiki/Curiously_recurring_template_p...) issues correctly. Nonetheless, very cool.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: