Wow, I am seriously seeing a pattern develop here. You really have a hard time understanding these simple concepts.
>something that automatic documentation has made harder by removing incentive, not easier
Yes, automating a task will remove incentive to do that task. Brilliant! And this whole time automation is used as incentive to do some task, but you have turned that whole idea on its head with your brilliance.
>Prove it, cock for brains.
Did, you didn't understand.
You claim straw man argument, but fail to even prove you used the correct word there. I chose a simple example that you see in many APIs on many platforms. So what I said was not a fallacy (hence no straw man claims to be made).
>Don't make an API that requires a fully qualified path, duh.
Depending on the scope of an API that is not always reasonable. And given that there is no standard, one can't know what they should expect by default.
How is one supposed to know if the argument is a fully qualified path, or a relative path to some other directory? If it is relative, from what directory are we starting? This is all answered in documentation, not paramnames. And if that documentation has some way of identifying that a certain piece of it refers to the pa ram in question, it can be more effectively utilized by tools (most notably IDE in this case) and be of greater use to the developer. Since creating the markup to make the documentation more useful is automated, it is no extra work for the developer to utilize.
I can't be more clear and I totally expect you to not understand that at all.
It is obvious you don't program enough of create sophisticated enough programs.