From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
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 19:15:43 +0200 [thread overview]
Message-ID: <87eefzp5c0.fsf@gnus.org> (raw)
In-Reply-To: <SA2PR10MB4474BE6B01A099C22F5CD641F37F9@SA2PR10MB4474.namprd10.prod.outlook.com> (Drew Adams's message of "Sun, 28 Mar 2021 16:39:29 +0000")
Drew Adams <drew.adams@oracle.com> writes:
>> > (plist-put (list 'a 'b 'c) "a" 42)
>> >
>> > Debugger entered--Lisp error: (wrong-type-argument plistp (a b c))
>> > plist-put((a b c) "abc" 42)
>> > eval((plist-put (list (quote a) (quote b) (quote c)) "abc" 42))
>> >
>> > That's all fine and dandy, except that there is no predicate `plistp'.
>>
>> The backtrace there doesn't seem to be a result of the example form,
>
> What do you mean by that?
The backtrace has "abc"; the code example does not.
> On the other hand, a probably more important question
> is the cost of getting the length of the list. That
> would be my main hesitation to say we should really
> have a `plistp' predicate.
Why? It's not like we'd use it for anything much.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-28 17:15 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 [this message]
2021-03-28 18:25 ` Drew Adams
2021-03-28 18:27 ` Lars Ingebrigtsen
2021-03-28 18:35 ` Drew Adams
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=87eefzp5c0.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47427@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).