GNU bug report logs - #50110
26.3; Doc of `assoc': TESTFN optional arg

Previous Next

Full log

Message #16 received at 50110-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 50110-done <at> debbugs.gnu.org
Subject: Re: [External] : Re: bug#50110: 26.3; Doc of `assoc': TESTFN optional
 arg
Date: Wed, 18 Aug 2021 22:08:53 +0300

> From: Drew Adams <drew.adams <at> oracle.com>
> CC: "50110 <at> debbugs.gnu.org" <50110 <at> debbugs.gnu.org>
> Date: Wed, 18 Aug 2021 18:41:00 +0000
> 
> > > Neither the `assoc' doc string nor the Elisp manual, node `Association
> > > Lists' explains the order of the args that get passed to TESTFN.
> > 
> > It's a function that tests 2 objects for equality, so why does the
> > order matter?
> > 
> > > It's just as reasonable to expect that the pattern is the first arg to
> > > TESTFN, instead of, as is actually the case, the second arg.
> > 
> > There's no "pattern" in the doc string, so I don't think I understand
> > what you are describing here.
> 
> I gave examples.  What part is unclear?  To know how to use
> `string-match-p' for testing you need to know the arg order
> for TESTFN.  The arg order matters for `string-match-p'.

OK, I added description of how TESTFN is called.

Previous Next

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