From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: No return value in doc string
Date: Wed, 26 Apr 2006 20:34:07 +0300 [thread overview]
Message-ID: <ud5f4gs1c.fsf@gnu.org> (raw)
In-Reply-To: <87y7xv3jja.fsf@hans.local.net> (message from Dieter Wilhelm on Mon, 24 Apr 2006 02:27:05 +0200)
> From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
> Date: Mon, 24 Apr 2006 02:27:05 +0200
>
> Is there any policy for the documentation string of the return value?
I don't know if there is a policy, but I think return values should be
documented.
> The Elisp programming guidelines just mention that the documentation
> string for functions should answer the question "What does this
> function do?".
That includes what value it returns, IMHO.
> So I'd consider leaving out the return value in a doc
> string of an interactive function a failure (please have a look at
> `next-line' `previous-line' and `make-frame').
What version of Emacs do you have? In the current development
sources, the doc string of make-frame already says:
Return a newly created frame displaying the current buffer.
So the return value, which is the frame object, is already documented.
As for the other two, the return nil, i.e. nothing, so I think it's
okay to say nothing about the (absent) return value.
That said,...
> Should I report this as bugs or is this a bit over the top?
...feel free to report if you disagree with my reasoning.
next prev parent reply other threads:[~2006-04-26 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 0:27 No return value in doc string Dieter Wilhelm
2006-04-26 17:34 ` Eli Zaretskii [this message]
2006-04-27 1:16 ` Dieter Wilhelm
[not found] <mailman.965.1146057882.9609.help-gnu-emacs@gnu.org>
2006-04-27 20:07 ` Stefan Monnier
2006-04-29 10:01 ` Dieter Wilhelm
[not found] ` <mailman.1122.1146330818.9609.help-gnu-emacs@gnu.org>
2006-04-29 21:55 ` Miles Bader
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=ud5f4gs1c.fsf@gnu.org \
--to=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.