GNU bug report logs - #47427
26.3; 1. Please define a built-in predicate `plistp', 2. wrong type wrong-type-argument error

Previous Next

Full log

Message #17 received at 47427 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: "47427 <at> debbugs.gnu.org" <47427 <at> debbugs.gnu.org>
Subject: RE: [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:25:31 +0000

> The backtrace has "abc"; the code example does not.

Yeah, sorry; typo.

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

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 could of course have a `plistp' predicate without
using it to test during `plist-put' etc.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.