http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24985
--- Comment #46 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-13 12:31:41 UTC --- (In reply to comment #45) > (In reply to comment #42) > > Yes, I like that, too. For reference, the following: > > > > note: candidate 'void f()' expects 0 arguments, 1 provided > > void f(); void f(int,int); > > ^ > > note: candidate 'void f(int, int)' expects 2 arguments, 1 provided > > void f(); void f(int,int); > > ^ > > I like this for this example, but does it work as well if the function name is > very long, and the "expects 2 arguments, 1 provided" is no longer in a > predictable position, but pushed off to the right of a very long line? I see your point, I am convinced. > (we do already have this problem when printing ridiculous paths for stdlib > headers with superfluous lib/gcc/x86_64-unknown-linux-gnu/4.8.0/../../../.. > rubbish in them, is there an existing bug for that?) Please open one with a reproducible testcase and I will take a look. This is very annoying to me as well, and there should be a way to make these paths shorter.
