D15532: [Astyle] Add Objective C to list of languages with formatters
René J.V. Bertin
noreply at phabricator.kde.org
Sat Sep 22 09:14:34 BST 2018
rjvbb added a comment.
> Eventually we have to compile our code anyway, so aren't we all dependent on the compiler?
Not what I meant of course. I don't need the compiler to tell me where a break isn't needed; I prefer to remind myself of such things and that I'm putting it there anyway (because the compiler won't be able to tell me I really forgot to use one, not unless you make some kind of "no break here" statement obligatory). In a sense this really isn't that different from wondering why you need to add a closing brace after a return...
Remember the old advice of always adding a default case to a switch, and putting a break in that one too (which isn't required either). I did notice the other day that kdevelop's build system now adds a flag that causes a compiler error when a switch statement is incomplete and/or lacks a default case.
> I'm not sure why you're bringing Modula-2 into the discussion
Because it's a lot stricter than C++ and at the same time a whole lot simpler. Yet even that language (like Pascal) doesn't require to put a closing semicolon in the last position where it would be required; I always put them anyway (and had a colleague who loved removing them).
My attitude towards this sort of thing may depend on the fact that my native language is Dutch (which has a grammar that's basically defined by exceptions) but that's a discussion for another place and time :)
> With KDevelop's nice integration of compiler warnings it usually doesn't hurt to turn on `-Weverything`. It helps me see a lot of issues that I'd probably overlook otherwise.
Honestly, I've seen better and the more warnings you get the less usable the contextual parser becomes because it can no longer display its information (all the more annoying if you need that information to correct an error). That contextual parser ("KIntelliSense" ^^) is among the main reasons that got me hooked on KDevelop btw.
I also still spend a lot of time coding in vi.
> If you don't want your compiler to tell you what (not) to do, use a language that isn't compiled.
Not necessary, just use C O:-)
To: rjvbb, #kdevelop, kossebau, kfunk
Cc: aaronpuchert, kfunk, pino, kossebau, kdevelop-devel, glebaccon, antismap, iodelay, vbspam, geetamc, Pilzschaf, akshaydeo, surgenight, arrowd
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel