2 ms·
It kind of fits how we'd talk in natural language about many common fragments of code. I mean, if I write a small function doSomething(inputDataString) then wh
by PeterisP 12y ago
It kind of fits how we'd talk in natural language about many common fragments of code.
I mean, if I write a small function doSomething(inputDataString) then when talking about what the function does, I'd just refer to "the string" or "that string" as there really can be no more meaningful name to refer to that. If there are multiple such parameters, only then names start making sense.
Similarly for iteration constructs like java 'for (Foobar foobar : foobars)' - when you're talking about what is done with that single instance of foobar, you just refer to it as 'a foobar' or 'every foobar', and a specific name is often meaningless if you don't need to distinguish it from others.