3 ms·
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 sorr
by to3m 11y ago
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.
- coldpie 11y ago> 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 :( Can you clarify what your objection is?
- RussianCow 11y agoI think they meant they're sorry that you previously had to manually find the file/line after an error.
- superuser2 11y agoThis has been a standard feature of an IDE since forever; it's disappointing that the plain-text editor community has just cracked it.
- Narishma 11y agoWhat do you mean 'just'? It's been in emacs and vim as far back as I can remember. At least for C and C++.
- superuser2 11y ago"Just" as in it's being listed as a feature rather than a baseline expectation, I think is parent's point.
- ori_b 11y agoDefine "just". I think plain text editors have been doing this for 30 years or more.
- to3m 11y agoShouldn't people be expecting this as a matter of course? I say they should.