Closed oleg68 closed 11 months ago
@oleg68 Yes, your last versions are much better!
@oleg68 If you're not intending to expand upon the parameter comments, then at least add a TODO to remove the comments that are only temporary work additions when the final commit that resolves the issue is due. But better would be to really add the explanations to the comments that would perhaps be useful in the future!
@larspalo
The description of parameters should be at the method specification, not at the method call.
Some other programming langualges (ex. Oracle pl/sql, Kotlin etc) allow not only positional notation but also naming notation of passing parameters. It makes the calling code more readable.
Unfortunally c++ does not support naming notation. Putting the parameter names to the comments is the only possible workaround.
So I insist on parameter names in the comments. I hope it will help other future developers.
So I insist on parameter names in the comments. I hope it will help other future developers.
And I insist that they are better than they are currently.
The description of parameters should be at the method specification, not at the method call.
Agree on that
So I insist on parameter names in the comments. I hope it will help other future developers.
And I insist that they are better than they are currently.
OK. I added a TODO of removing the parameter name comments in the future after reducing the number of parameters of DoCrossfade
@oleg68 Ok, fair enough. Except that the comments are prime examples of poor comment practice, I never saw the need of them to begin with as when hovering over the function call in Eclipse IDE I could see the parameters directly as a reference. Don't know if it works the same in Netbeans though...
Don't know if it works the same in Netbeans though
Netbeans does not show the parameter names.
We'll just have to remember this later.
I have already started working on it, but it is not so simple.
@oleg68 Sure, more or less every IDE behaves differently. This is what I see:
I have already started working on it, but it is not so simple.
I understand that. Thanks for your efforts!
This is the first PR related to #1724
This PR makes the code a little bit clear
const
qualifier to lots of GetXXX() methodsoverride
qualifier to lots of methodsNo GO behavior should be changed.