From: Tino Calancha <tino.calancha@gmail.com>
To: emacs-devel@gnu.org
Subject: RE: humble proposal: New special form progn-1
Date: Thu, 28 Jul 2016 20:35:30 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1607282024550.21161@calancha-pc> (raw)
In-Reply-To: <54a95c7d-a709-4dba-b72b-68fbd063a916@default>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On Wed, 27 Jul 2016, Drew Adams wrote:
> and sometimes for a return-value computation that is followed by
> some side effect such as showing a message.
>
> But for most cases where someone else might use `prog1' I'm already
> let-binding a variable that I use for the value that might otherwise
> be returned by the `prog1' (or by a `prog2').
>
> (let (... result) ... (setq result ...) ... result)
Yeah, i also like binding one 'result' variable: this way
all defun's in the code sistematically return
the last evaluated form. Its easier to read.
On Wed, 27 Jul 2016, Clément Pit--Claudel wrote:
>No, that's not what I meant. I meant that in Lisp when I want to write
>(n - 1) I actually write (- n 1); thus, when I see progn-1,
>I don't read it as "prog (n minus 1)", but instead as "progn dash 1".
>Given the convention that foo-1 usually means
>"internal function used in the implementation of foo",
>I read it as "internal function used to implement progn".
This is another point against my proposal: the notation could be
misleading.
So, i give up with my proposal.
Thank you very much.
Tino
next prev parent reply other threads:[~2016-07-28 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:16 humble proposal: New special form progn-1 Tino Calancha
2016-07-27 12:22 ` Stefan Monnier
2016-07-27 12:53 ` Andreas Schwab
2016-07-27 13:58 ` Tino Calancha
2016-07-27 16:04 ` Andreas Schwab
2016-07-27 14:08 ` Clément Pit--Claudel
2016-07-27 14:30 ` Phil Sainty
2016-07-27 15:15 ` Drew Adams
2016-07-28 11:35 ` Tino Calancha [this message]
2016-07-27 14:38 ` Tino Calancha
2016-07-27 19:07 ` Clément Pit--Claudel
2016-07-27 21:51 ` Nicolas Petton
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=alpine.DEB.2.20.1607282024550.21161@calancha-pc \
--to=tino.calancha@gmail.com \
--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 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.