unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	65030@debbugs.gnu.org, eller.helmut@gmail.com,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#65030: 30.0.50; Check keyword args of make-process
Date: Tue, 08 Aug 2023 10:52:36 +0200	[thread overview]
Message-ID: <87sf8tapbf.fsf@gmail.com> (raw)
In-Reply-To: <D16021F8-7D7E-49F0-971E-32B040E303BF@acm.org> ("Mattias Engdegård"'s message of "Sun, 6 Aug 2023 10:49:59 +0200")

>>>>> On Sun, 6 Aug 2023 10:49:59 +0200, Mattias Engdegård <mattiase@acm.org> said:

    Mattias> 6 aug. 2023 kl. 06.58 skrev Eli Zaretskii <eliz@gnu.org>:
    >> Any specific comments to the proposed patch?  Or do you think it is
    >> good to go?

    Mattias> Good to go as far as I'm concerned. It will be genuinely useful, and I
    Mattias> see no serious problems with the implementation.

    Mattias> It can be extended but that would not prevent it from being committed
    Mattias> as-is. For example, something that detects omitted values in the
    Mattias> middle, not just the end, of the argument list. (The feasibility of
    Mattias> this depends on the likelihood of argument values being keywords
    Mattias> themselves.)

I donʼt think any of the `make-process' keywords accept keywords as
values, but missing values tends to cause catastrophic failure, so I
donʼt think itʼs that common a mistake.

    Mattias> The main objection is that `make-process`, due to its design, is often
    Mattias> called indirectly using `apply` which would not trigger the
    Mattias> application of this compiler macro, so perhaps we should improve the
    Mattias> error handling of Fmake_process instead.

As long as that improvement results in warnings for mistakes such as
misspelled keywords, rather than errors.

Robert
-- 





  reply	other threads:[~2023-08-08  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  6:47 bug#65030: 30.0.50; Check keyword args of make-process Helmut Eller
2023-08-05  9:21 ` Eli Zaretskii
2023-08-05 23:07   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-06  4:58     ` Eli Zaretskii
2023-08-06  8:49       ` Mattias Engdegård
2023-08-08  8:52         ` Robert Pluim [this message]
2023-08-08  9:16           ` Mattias Engdegård
2023-08-08  9:27             ` Robert Pluim
2023-08-08  9:42               ` Mattias Engdegård
2023-08-08 12:16             ` Eli Zaretskii
2023-08-08 13:05               ` Mattias Engdegård
2023-08-08 13:18                 ` Robert Pluim
2023-08-08 16:38                   ` Mattias Engdegård
2023-08-08 17:14                     ` Helmut Eller
2023-08-08 20:15                       ` Mattias Engdegård
2023-08-08 17:43                     ` Eli Zaretskii
2023-08-08 17:51                       ` Mattias Engdegård
2023-08-08 17:54                       ` Stefan Kangas
2023-08-08 18:28                         ` Eli Zaretskii
2023-08-08 13:37           ` Visuwesh
2023-08-08 13:52             ` Robert Pluim

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=87sf8tapbf.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=65030@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    /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).