From: Ricard Wanderlof <ricard.wanderlof@axis.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Stop putting function comments in foo.h
Date: Tue, 18 Mar 2014 07:47:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1403180845360.26118@lnxricardw1.se.axis.com> (raw)
In-Reply-To: <53276F7C.7000105@earthlink.net>
>>> I ask because every time I find a "See foo.h." comment I get depressed
>>> and disappointed. They're just getting in my way, and I'm wondering
>>> if it's just me.
>>
>> Whenever I look at a header file that doesn't document its
>> functions' interfaces (and often doesn't even list the
>> parameter names), I get depressed and disappointed. I'm
>> wondering if it's just me. :-)
One solution would be to simply duplicate the documentation in both the .c
and .h files. Sure, it's duplicated text, and there's always the
possibility that they'll get out of sync with each other, but at least
we're putting the burdon on whoever is writing the code, not whoever is
reading it, which makes sense since the code will be read many more times
than it is (re)written.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
next prev parent reply other threads:[~2014-03-18 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 19:45 Doug Evans
2014-03-16 9:51 ` Gerhard Gappmeier
2014-03-17 0:38 ` Yao Qi
2014-03-17 13:44 ` Joel Brobecker
2014-03-17 14:23 ` Sergio Durigan Junior
2014-03-17 16:09 ` Pedro Alves
2014-03-17 17:15 ` DJ Delorie
2014-03-17 21:59 ` Stan Shebs
2014-03-18 7:47 ` Ricard Wanderlof [this message]
2014-03-18 15:59 ` Doug Evans
2014-03-26 16:45 ` Doug Evans
2014-03-26 19:05 ` Doug Evans
2014-03-26 20:43 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1403180845360.26118@lnxricardw1.se.axis.com \
--to=ricard.wanderlof@axis.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox