all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 18:39:19 +0200	[thread overview]
Message-ID: <BANLkTi=1eOtpTA=J8JwReizEdBsQ_ZHsCA@mail.gmail.com> (raw)
In-Reply-To: <jwv8vsvkv0y.fsf-monnier+emacs@gnu.org>

On Tue, Jun 21, 2011 at 18:33, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> No, I do not systematically oppose side-effecting functions which return
> a value as well.  That would be much too drastic (e.g. how would you
> figure out which window was used by `display-buffer'?).
> I;.e. the return value is really indispensable.  Contrast this with
> set-process-buffer whose return value is always available to the caller
> before even calling it.

OK, that makes sense.

Thanks,

    Juanma



  reply	other threads:[~2011-06-21 16:39 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
2011-06-21 16:33             ` Stefan Monnier
2011-06-21 16:39               ` Juanma Barranquero [this message]
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='BANLkTi=1eOtpTA=J8JwReizEdBsQ_ZHsCA@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 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.