3 ms·
And including ANY comment in code - as in, mixing code and comments in the same file - means that your workflow doesn't support external documentation keyed to
by logicallee 11y ago
And including ANY comment in code - as in, mixing code and comments in the same file - means that your workflow doesn't support external documentation keyed to branches, hashes, filenames, and line numbers.
Likewise, naming variables, functions, classes, and continuously typing out the same name over and over again means that your language and IDE is not rich enough to contain pronouns, making you have to type tediously instead of something even sightly more natural.
Why don't we improve languages so that they have pronouns for the stuff you're doing right there? Why don't comments get linked to line numbers in some external layer? And why would anyone commit commnented-out code to a repository?
The only answer to all of the above is that we are living in 2015 and not some future year. you work with what you have.
- imtringued 11y agoWe have those "tedious" things because programmers don't like ambiguity.
- dTal 11y ago>Why don't we improve languages so that they have pronouns for the stuff you're doing right there? Interestingly, we do sort of have that - in most CAS interfaces "Ans" can be used to refer to the last calculated value. A lot of programming REPLs can do this sort of thing too. Another example might perhaps be Bash's $1, $2, $3 etc for positional arguments.