From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Deniz Dogan <deniz@dogan.se>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r104642: * src/process.c (Fset_process_buffer): Clarify return value in docstring.
Date: Tue, 21 Jun 2011 16:30:38 +0200 [thread overview]
Message-ID: <BANLkTin=NjqoxMRy1Dg4ABmh12yCApox=Q@mail.gmail.com> (raw)
In-Reply-To: <jwv1uynnukb.fsf-monnier+emacs@gnu.org>
On Tue, Jun 21, 2011 at 16:13, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> People usually aren't afraid to use undocumented features.
And if they were 300+ uses of set-process-buffer in the sources,
instead of 19, someone would have.
> As a general rule, yes.
What about `display-buffer'? It certainly exists for its side effect,
but it returns the window, a fact which is both documented and used.
If it were a new function, would you oppose doing so?
I'm not arguing, mind you, just trying to understand why it is OK for
some functions whose whole purpose is side-effects to return a useful
value, and not OK for others.
Juanma
next prev parent reply other threads:[~2011-06-21 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QYeLs-00050O-9O@colonialone.fsf.org>
2011-06-20 14:26 ` [Emacs-diffs] /srv/bzr/emacs/trunk r104642: * src/process.c (Fset_process_buffer): Clarify return value in docstring Stefan Monnier
2011-06-20 16:16 ` Juanma Barranquero
2011-06-20 17:53 ` Stefan Monnier
2011-06-20 19:53 ` Juanma Barranquero
2011-06-21 14:13 ` Stefan Monnier
2011-06-21 14:30 ` Juanma Barranquero [this message]
2011-06-21 16:33 ` Stefan Monnier
2011-06-21 16:39 ` Juanma Barranquero
2011-06-21 20:17 ` Deniz Dogan
2011-06-22 1:59 ` Stefan Monnier
2011-06-21 4:10 ` Stephen J. Turnbull
2011-06-21 16:00 ` Deniz Dogan
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='BANLkTin=NjqoxMRy1Dg4ABmh12yCApox=Q@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=deniz@dogan.se \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).