From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: Changes in revision 114466
Date: Mon, 30 Sep 2013 13:47:44 +0200 [thread overview]
Message-ID: <524964E0.4040607@online.de> (raw)
In-Reply-To: <8c8eb64b-74ca-4fba-bb35-a799582423da@default>
Am 30.09.2013 07:21, schrieb Drew Adams:
>> But I see one problem: not every {functions, variables, ...} needs
>> documenting. E.g., some functions/variables use two hyphens to separate
>> prefix. These functions/variables usually don't needs documenting.
>
> Why not? Do you think developers do not need documentation?
>
>> IMO every user option and every command needs documentation.
>
> IMO also. And pretty much every function, variable, face, widget,...
> Why not?
>
>
IMO that depends, in some cases would welcome that.
OTOH a lot is either trivial or the kind, I would want to read the code, no explanations, maybe run with edebug.
Some comments inside the code seem best than.
next prev parent reply other threads:[~2013-09-30 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.53349.1380335551.10747.emacs-diffs@gnu.org>
2013-09-28 7:46 ` Changes in revision 114466 Eli Zaretskii
2013-09-28 22:30 ` Xue Fuqiao
2013-09-29 2:36 ` Eli Zaretskii
2013-09-29 7:24 ` Thien-Thi Nguyen
2013-09-30 4:55 ` Xue Fuqiao
2013-09-30 5:21 ` Drew Adams
2013-09-30 10:29 ` Stephen Berman
2013-09-30 15:05 ` Drew Adams
2013-09-30 15:52 ` Thien-Thi Nguyen
2013-10-01 2:11 ` Stephen J. Turnbull
2013-09-30 15:42 ` Eli Zaretskii
2013-09-30 11:47 ` Andreas Röhler [this message]
2013-09-30 15:38 ` Eli Zaretskii
[not found] ` <<83k3hye2uq.fsf@gnu.org>
2013-09-30 16:38 ` Drew Adams
2013-10-01 3:40 ` Xue Fuqiao
2013-10-01 4:57 ` Stephen J. Turnbull
2013-10-01 5:15 ` Drew Adams
2013-10-01 5:27 ` Drew Adams
2013-10-01 6:11 ` Stephen J. Turnbull
2013-10-01 7:44 ` Drew Adams
2013-10-01 8:29 ` Stephen J. Turnbull
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524964E0.4040607@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).