From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
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 10:13:34 -0400 [thread overview]
Message-ID: <jwv1uynnukb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <BANLkTimtmUsLpp7Yy0q361m6G2pd8BbO0Q@mail.gmail.com> (Juanma Barranquero's message of "Mon, 20 Jun 2011 21:53:28 +0200")
>> I can't find a single example of Elisp code in Emacs that does not
>> ignore the return value of set-process-buffer
> Hardly surprising, as it was undocumented.
People usually aren't afraid to use undocumented features.
>> (and that's a good thing).
> Perhaps. Do you oppose also to using the return value of other
> side-effecting functions or special forms,
As a general rule, yes.
> like `setq'? Because there's no shortage of "(if (setq", "(and (setq",
> "(or (setq" in the sources (341, 387 and 54 instances, respectively).
Indeed, setq is used this way fairly often, so it's pointless to try and
oppose it. As a matter of fact, I do use this sometimes myself.
Stefan
next prev parent reply other threads:[~2011-06-21 14:13 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 [this message]
2011-06-21 14:30 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv1uynnukb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=deniz@dogan.se \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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.