Re: FWD:Re: refactoring
Stefan Seefeld <[email protected]>
| Newsgroups | gmane.comp.documentation.synopsis |
|---|---|
| Message-ID | <[email protected]> |
David Abrahams wrote: > Stefan Seefeld <[email protected]> writes: > > >>It would for example be of great value to have a C++ parser >>that would - similar to wave - trace the processing of source code >>and thus help users better understand their code and C++ in general. >>Gone are the days of huge incomprehensible error messages when using >>template-heavy code. :-) > > > If you read chapter 8 of > http://boost-consulting.com/metaprogramming-book.html, you'll know I > think most compilers could do way more to make sure those error > messages are comprehensible, and that most of the information in there > is actually essential. At best a tracing C++ compiler will add _more_ > info (not that it wouldn't be useful info). I think the only way to > really reduce the reams of output is with concept checking, either in > a library, or better, in a language feature. > I agree. I was actually thinking of traces of all the decisions a compiler does implicitely when looking up symbols, instantiating templates (SFINAE !), etc., because without these a generated error may be quite misleading. Concept checks would be nice, too. I wonder how Richard Kelly's work with synopsis is going... Regards, Stefan