GNU bug report logs - #23926
defcustom with STANDARD=<non-constant-expression> gives confusing results

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: npostavs <at> users.sourceforge.net
Cc: 23926 <at> debbugs.gnu.org
Subject: Re: bug#23926: defcustom with STANDARD=<non-pure-expression> gives
 confusing results
Date: Tue, 12 Jul 2016 08:20:05 +0300

> From: npostavs <at> users.sourceforge.net
> Cc: 23926 <at> debbugs.gnu.org
> Date: Mon, 11 Jul 2016 23:26:25 -0400
> 
> I had a look at the docs; seems to me "standard" is used consistently,
> so it makes sense to change to that.  Docstring of defcustom:

I'm in favor of using consistent terminology, but this:

>     STANDARD is an expression specifying the variable’s standard
>     value.

is just tautology: it doesn't really explain what is STANDARD, except
by using the same word, which is too general to explain itself.

So if we want to use this, and consider that an improvement, I think
it would be good to explain some more what "standard value" means or
is.

Thanks.

Previous Next

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