unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen via "Emacs development discussions."
	<emacs-devel@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>
Subject: Re: master 930c578c104: ; Improvements to PEG documentation
Date: Tue, 16 Apr 2024 20:54:41 -0700	[thread overview]
Message-ID: <87jzkwlk3i.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87frvk90it.fsf@web.de> (Michael Heerdegen via's message of "Wed,  17 Apr 2024 04:38:18 +0200")

Michael Heerdegen via "Emacs development discussions."
<emacs-devel@gnu.org> writes:

> Hello Eric,
>
> why do you use the term "lambda form" here?
>
> | +@defun peg-run peg-matcher &optional failure-function success-function
> | +This function accepts a single @var{peg-matcher}, which is the result of
> | +calling @code{peg} (see below) on a named rule, usually the entry-point
> | +of a larger grammar.
> | +
> | +At the end of parsing, one of @var{failure-function} or
> | +@var{success-function} is called, depending on whether the parsing
> | +succeeded or not.  If @var{success-function} is called, it is passed a
> | +lambda form that runs all the actions collected on the stack during
> | +parsing -- by default this lambda form is simply executed.
>
> AFAIU the function is just passed a function.  An anonymous function
> maybe, but certainly a function value, not a function form - so just
> daily business - or do I miss something?

No, you're right, I was probably just looking at the code and describing
what I was seeing.



  reply	other threads:[~2024-04-17  3:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171323742013.5283.3736155251539337632@vcs2.savannah.gnu.org>
     [not found] ` <20240416031700.9D2B1C1FB45@vcs2.savannah.gnu.org>
2024-04-16 10:00   ` master 930c578c104: ; Improvements to PEG documentation Michael Albinus
2024-04-16 10:05     ` Mattias Engdegård
2024-04-17  0:33       ` Eric Abrahamsen
2024-04-17  2:38         ` Michael Heerdegen via Emacs development discussions.
2024-04-17  3:54           ` Eric Abrahamsen [this message]
2024-04-19 23:28             ` Eric Abrahamsen
2024-04-20 23:39               ` Michael Heerdegen via Emacs development discussions.
2024-04-21  0:51                 ` Eric Abrahamsen
2024-04-17 12:26         ` Eli Zaretskii

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=87jzkwlk3i.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).