Subject: Re: [External] : Re: bug#47427: 26.3; 1. Please define a built-in predicate `plistp', 2. wrong type wrong-type-argument error

From: Lars Ingebrigtsen <[email-masked]>
Date: Sun, 28 Mar 2021 20:27:54 +0200

Drew Adams <[email-masked]> writes:

> 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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no