> This is not a matter of pleasing anybody, it is a matter of being able to work
> efficiently with the code and be able to focus on the problem, not the layout.
> For that reason, such things as "pleasing the machine" *may* be important
> because the tools are not good enough (not saying that they are in this case).
They aren't good enough in this case. Visual Studio has no problem at
all finding the declaration and the definition of a function with or
without parameter names.
Even with the ctags argument, it is very bad practice to not include the
parameter names in the prototypes in the header. That is the interface
to the module. We should not *require* a coder to look into the source
file to know what to do in all cases. Even with functions where a coder
is very well versed in what it does he or she may forget the order of
parameters. Given a prototype such as void CopyString(char *, int,
char *, int), does the source or dest come first? The coder would have
to look in the source to know for sure and likely would have to sort
through both public and non-public functions.