From: Mark Oteiza <mvoteiza@udel.edu>
To: npostavs@users.sourceforge.net
Cc: 28254@debbugs.gnu.org
Subject: bug#28254: 26.0.50; SRFI-2 and-let*
Date: Sat, 2 Sep 2017 00:14:24 -0400 [thread overview]
Message-ID: <20170902041424.GA21189@holos.localdomain> (raw)
In-Reply-To: <878thx7qcc.fsf@users.sourceforge.net>
On 01/09/17 at 11:05pm, npostavs@users.sourceforge.net wrote:
>Mark Oteiza <mvoteiza@udel.edu> writes:
>
>> (and-let* ((x ...)
>> (y ...)
>> ((x > y)))
>> ...)
>
>I assume you meant (> x y), unless you've managed to somehow squeeze an
>infix expression parser into that patch above ;)
Ah yeah, I wish!
>> I didn't try writing it in the style of if-let*--perhaps if-let* could
>> be extended and all three macros would learn (EXPR).
>
>Yes, I think it's best if all foo-let* macros interpret the varlist in
>the same way.
Alright, I'll look at it.
next prev parent reply other threads:[~2017-09-02 4:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 20:11 bug#28254: 26.0.50; SRFI-2 and-let* Mark Oteiza
2017-09-01 2:55 ` npostavs
2017-09-02 2:10 ` Mark Oteiza
2017-09-02 3:05 ` npostavs
2017-09-02 4:14 ` Mark Oteiza [this message]
2017-09-02 5:25 ` Michael Heerdegen
2017-09-02 13:36 ` Mark Oteiza
2017-09-02 18:41 ` Noam Postavsky
2017-09-03 17:48 ` Michael Heerdegen
2017-09-03 22:39 ` Mark Oteiza
2017-09-04 0:48 ` Mark Oteiza
2017-09-04 14:12 ` Michael Heerdegen
2017-09-05 3:47 ` Mark Oteiza
2017-09-05 15:04 ` Michael Heerdegen
2017-09-06 12:12 ` Michael Heerdegen
2017-09-06 13:06 ` Mark Oteiza
2017-09-06 19:04 ` Michael Heerdegen
2017-09-04 1:13 ` Mark Oteiza
2017-09-05 3:55 ` Mark Oteiza
2017-09-09 0:33 ` Mark Oteiza
2017-09-12 12:39 ` Michael Heerdegen
2017-09-12 13:09 ` Mark Oteiza
2017-09-12 18:44 ` Michael Heerdegen
2017-09-12 20:21 ` Mark Oteiza
2017-09-13 10:16 ` Michael Heerdegen
2017-09-13 11:48 ` Mark Oteiza
2017-09-13 16:46 ` Michael Heerdegen
2017-09-13 16:49 ` Mark Oteiza
2017-09-13 17:05 ` Michael Heerdegen
2017-09-13 17:28 ` Mark Oteiza
2017-09-13 17:49 ` Michael Heerdegen
2017-09-12 12:13 ` Michael Heerdegen
2017-09-12 14:29 ` Mark Oteiza
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=20170902041424.GA21189@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=28254@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.