[RFC] Stop putting function comments in foo.h

[Doug Evans]

On Mon, Mar 17, 2014 at 9:07 AM, Pedro Alves <palves@redhat.com> wrote:
> IMO, a module's API documentation should be in its header file, as
> that's where the module's "public" contract is defined.
> Needing to peek at the module's implementation feels wrong to me.
> If the function's documentation isn't clear without looking
> at the function's body, something is already wrong with
> the comment.

It use to be that M-. took me to the function definition and its documentation.

I'm curious what other emacs+etags users do now.