2 ms·
I don't think scare quotes are warranted, I do prefer the former style, I find that it makes it easier to match the arguments to the function at a glance. Of co
by simias 8y ago
I don't think scare quotes are warranted, I do prefer the former style, I find that it makes it easier to match the arguments to the function at a glance. Of course it's purely subjective.
I do note that even your proposition doesn't really solve the problem of using Elastic TabStops, because if you imagine a comment spanning all three lines:
someLongFunctionCall(⇥ /* This function call */
⇥ longVariableName1,⇥ /* is really cool *
⇥ longVariableName2);⇥ /* and stuff */
You have an additional tab at the beginning of the two last lines which means (as far as I understand it) that the first comment line won't necessarily line up with the two others. Of course that showcases a potential issue with Elastic TabStops, not your particular coding style.
- guitarbill 8y agoBlock comments interleaved with code are rare in most codebases I've worked on, because it's almost always easier to put them on their own lines, above the statement: /* This function call is really cool and stuff */ someLongFunctionNameThatWillBeRefactored( longVariableName1, longVariableName2); So I sort of dismissed that use-case as a toy example. But yes, if you did that elastic tabstops would be useful... except the contents of the block comment doesn't get reflowed when the tabstop width changes. Which I'm sure we could do, but then we're getting into interesting territory w.r.t edge cases/usability for sure.