I'm a bit sad that "editor takes to you location of compile error" is actually touted as a feature! It's one thing to have to do this occasionally, but I'm sorry to hear that people are used to doing it all the time :(
Nevertheless the error message point is good. It's ridiculous how atrocious error messages can be. (And they probably seem even worse if you have to find the file+line yourself.) This is actually pretty straightforward to implement, and supported directly with flex+bison, so it's a shame that it's not more commonplace.
Perhaps in the early days of gcc it was seen as too much overhead? Anyway, should be de rigeur for anything being embarked upon today.
> I'm a bit sad that "editor takes to you location of compile error" is actually touted as a feature! It's one thing to have to do this occasionally, but I'm sorry to hear that people are used to doing it all the time :(
Nevertheless the error message point is good. It's ridiculous how atrocious error messages can be. (And they probably seem even worse if you have to find the file+line yourself.) This is actually pretty straightforward to implement, and supported directly with flex+bison, so it's a shame that it's not more commonplace.
Perhaps in the early days of gcc it was seen as too much overhead? Anyway, should be de rigeur for anything being embarked upon today.