From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "47427@debbugs.gnu.org" <47427@debbugs.gnu.org>
Subject: bug#47427: [External] : Re: bug#47427: 26.3; 1. Please define a built-in predicate `plistp', 2. wrong type wrong-type-argument error
Date: Sun, 28 Mar 2021 18:35:57 +0000 [thread overview]
Message-ID: <SA2PR10MB447437C29166F3715166214AF37F9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a6qnp1zp.fsf@gnus.org>
> > I meant that if we really had an (accurate) error msg
> > saying that the plist wasn't proper then in order to
> > test that for each `plist-put' or whatever we'd have
> > to traverse every plist argument, to see if it really
> > is proper.
> >
> > To test that `(a b c)' isn't a proper plist we'd need
> > to check that the number of elements is even.
>
> We are not going to check that, because it wouldn't be
> backwards-compatible.
Good.
If we don't use `plistp' in such cases then it's fine to
add it. And it's not important to do so.
Then see my previous msg about the real problems.
This bug really shouldn't be about adding a `plistp'
predicate, as I indicated. It all depends on how you
intend to deal with the real problems.
next prev parent reply other threads:[~2021-03-28 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 22:27 bug#47427: 26.3; 1. Please define a built-in predicate `plistp', 2. wrong type wrong-type-argument error Drew Adams
2021-03-28 12:50 ` Lars Ingebrigtsen
2021-03-28 16:39 ` bug#47427: [External] : " Drew Adams
2021-03-28 17:15 ` Lars Ingebrigtsen
2021-03-28 18:25 ` Drew Adams
2021-03-28 18:27 ` Lars Ingebrigtsen
2021-03-28 18:35 ` Drew Adams [this message]
2022-06-27 10:37 ` 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=SA2PR10MB447437C29166F3715166214AF37F9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=47427@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).