GNU bug report logs - #76055
29.4; Doc of string-empty-p

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 76055 <at> debbugs.gnu.org
Subject: bug#76055: 29.4; Doc of string-empty-p
Date: Thu, 06 Feb 2025 10:06:24 +0200

> From: Drew Adams <drew.adams <at> oracle.com>
> CC: "76055 <at> debbugs.gnu.org" <76055 <at> debbugs.gnu.org>
> Date: Wed, 5 Feb 2025 21:13:05 +0000
> 
> > > To be more precise: Please do it for each
> > > such function where you can guess that this
> > > behavior isn't just a side effect or that's
> > > likely to be changed without notice.
> > 
> > How can anyone know that?
> 
> By looking at the name of the function and the
> function definition, and thinking about how
> the function is used and expected to be used?

Feel free to do this and suggest which functions you think should
document their support of symbols.  I personally think that you are
greatly underestimating how large and complex this job is, and
therefore I don't plan doing it myself, and would not encourage anyone
to do it.  I think the benefits are quite small compared with the
efforts.

> At least for _new_ functions that use primarily
> strings as args, the _author_ should know why it
> was decided to allow symbols instead of just
> strings.

You assume that it was a conscious decision, but that is not given at
all.  I dare to think that this assumption is simply false in most, if
not all, cases.

Previous Next

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