From: Tino Calancha <tino.calancha@gmail.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: humble proposal: New special form progn-1
Date: Wed, 27 Jul 2016 23:38:33 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1607272330350.25325@calancha-pc> (raw)
In-Reply-To: <3d003b0a-6d60-1081-5a6f-6324add22e79@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Wed, 27 Jul 2016, Clément Pit--Claudel wrote:
> On 2016-07-27 08:16, Tino Calancha wrote:
>> Dear all,
>>
>> i got this idea few days ago (see the patch at the end).
>>
>> Even though I envision that no one here will like this proposal,
>> for me it's instructive to learn from your answers why this is
>> not a good idea.
>
> :) I don't have anything strongly against it myself. Any reason to not make it a lisp macro though?
>
>> My (weak) motivation for introduce this is:
>>
>> * Compact (and familiar) syntaxis.
>> * Same reasons to exists as prog2 has (excluding historical reasons).
>> * Other way to acomplish one usual task.
>> * Allow lower indentation level (see below):
>
> Sounds good. One worry that I have with the name is that I read it as (progn)-(1), not prog(n-1).
You mean that could confuse some people that is like:
(1- (progn (form)))
I still like progn-1 more because naturally fit in the sequence:
prog1, prog2, ..., progn
> Wouldn't
> (progn
> (form1)
> ...
> (formN-2)
> (prog1
> (formN-1)
> (formN)))
> work?
Of course does. I didn't claim i exhausted the casuistic :-)
Thank you!
Tino
next prev parent reply other threads:[~2016-07-27 14:38 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
2016-07-27 14:38 ` Tino Calancha [this message]
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
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=alpine.DEB.2.20.1607272330350.25325@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=clement.pit@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 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).