5

Compilation errors with templates are often obscure and not easily decipherable unless one is really well versed with templates. Many times an expert programmer might as well be flummoxed by these. I am sure most of us have felt the pinch of it many a times.

As I understand the C++ standard only mandates implementations to provide a diagnostic for an ill-formed program but not how or what diagnostic messages shall be provided.
However, are there any guidelines laid out by the Standards committee to overcome this problem of not easily decipherable diagnostics (especially) in case of templates. Has this ever even come up for a discussion? Also, are the mainstream implementations doing something about or have planned about this issue?

The question is quite open ended for discussion but with the SO C++ community being one of the most active C++ communities I am sure someone somewhere must have at least some idea of this. Also, a few of Standards committee members (I know) actively participate on the C++ tag, I am hoping they might have some information on this if et al.

Bill the Lizard
  • 398,270
  • 210
  • 566
  • 880
Alok Save
  • 202,538
  • 53
  • 430
  • 533
  • clang++ is a good tool for this. The error message are much better than those of g++ and the ones I remember from VS2005 (I have not used VS extensively since). – David Rodríguez - dribeas May 24 '12 at 19:11
  • 1
    The answer to your question is [Concepts](http://en.wikipedia.org/wiki/Concepts_%28C%2B%2B%29). Unfortunately, they weren't ready for C++11. – Jesse Good May 25 '12 at 00:04

2 Answers2

5

You're asking two separate questions.

First of all, yes, mainstream implementations are doing something about it. It may not be a top priority for g++ or msvc, but those aren't the only mainstream implementations. It was one of the design goals behind clang (see http://clang.llvm.org/diagnostics.html), and at least at some point Intel listed better template errors as a selling point for ic++ over msvc.

Second, people on the standards committee discussed this in detail, and mostly agreed that concepts were a big part of the answer, which effectively means that it's been put off to the future since concepts were removed from the C++11 standard.

abarnert
  • 354,177
  • 51
  • 601
  • 671
3

It's definitely a problem, especially when people start doing tricky stuff with metaclasses. The only tool I know of that helps out a little bit is stlfilt, which "simplifies and/or reformats long-winded C++ error and warning messages, with a focus on STL-related diagnostics"

Edward Loper
  • 15,374
  • 7
  • 43
  • 52