unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19371@debbugs.gnu.org
Subject: bug#19371: 25.0.50; doc of functions and macros defined in macroexp.el
Date: Sat, 03 Aug 2019 00:33:14 +0200	[thread overview]
Message-ID: <87blx7jiz9.fsf@web.de> (raw)
In-Reply-To: <87v9vfl1d8.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Fri, 02 Aug 2019 23:10:43 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>  (defun macroexp-progn (exps)
> -  "Return an expression equivalent to \\=`(progn ,@EXPS)."
> +  "Return EXPS with `progn' prepended.
> +If EXPS is a single expression, `progn' is not prepended."
>    (if (cdr exps) `(progn ,@exps) (car exps)))

That's described a bit confusingly: AFAIU EXPS should always be a list
of expressions, and when it's _a_list_ of only one expression, `progn'
is not prepended and the expression is returned (and not EXPS as your
text suggests).  BTW, compared to that description I find the original
version much better (simpler).

> > 2. And then there is `macroexp-let2*', whose doc string says only to
> > bind each binding (bind a binding?!) "as `macrolet2' does".  That
> > means nothing.  Presumably, based on the `*' in the name, the behavior
> > is similar to that of `let*'.  If so, you can use the doc of `let*
> > as inspiration.
>
> Uhm...  I have no idea what it does:
>
> (defmacro macroexp-let2* (test bindings &rest body)
>   "Bind each binding in BINDINGS as `macroexp-let2' does."
>   (declare (indent 2) (debug (sexp (&rest (sexp form)) body)))
>   (pcase-exhaustive bindings
>     ('nil (macroexp-progn body))
>     (`((,var ,exp) . ,tl)
>      `(macroexp-let2 ,test ,var ,exp
>         (macroexp-let2* ,test ,tl ,@body)))))

You understand what macroexp-let2 does?  It supports one binding (a var
plus an expression, specified as separate arguments).  macroexp-let2*
supports a list of such pairs specified as BINDINGS, similar to let*.

The naming scheme `macroexp-let2' vs. `macroexp-let2*' is not ideal:
first, because `macroexp-let2' doesn't support multiple bindings like
`let', and secondly because, if I look at the use cases in the sources,
most of them just want to establish multiple bindings, but parallel
binding would suffice, so they actually want to non-stared version of
macroexp-let2*, which is not macroexp-let2 - AFAICT it doesn't exist.

Michael.






  reply	other threads:[~2019-08-02 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 19:04 bug#19371: 25.0.50; doc of functions and macros defined in macroexp.el Drew Adams
2019-08-02 21:10 ` Lars Ingebrigtsen
2019-08-02 22:33   ` Michael Heerdegen [this message]
2019-08-03 11:50     ` Lars Ingebrigtsen
2019-08-04 12:29       ` Michael Heerdegen
2019-08-04 12:44         ` Lars Ingebrigtsen

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=87blx7jiz9.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=19371@debbugs.gnu.org \
    --cc=larsi@gnus.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).