git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: On boolean configuration variables...

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 25, 2006, 14:00 UTC
Message-ID
<Pine.LNX.4.63.0606251553110.29667@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<e7m3b6$eoa$1@sea.gmane.org>
Hi,
On Sun, 25 Jun 2006, Anand Kumria wrote:
> Allowing 'yes' and 'no' to equal 'true' and 'false' respectively sounds
> pretty sane and user-friendly.
> 
> Why wouldn't you want to do that?
'Cause you'd have to add "maybe", too ;-)

Seriously, there is a subtle side to booleans, which is the reason that they typically take on only "false" and "true": Consider the question "Is the box not red?". If the answer is "yes", I do not know if "yes, the box is red" or "yes, the box is not red".

"true" and "false" are less ambiguous.

Ciao, Dscho

Previous: Anand KumriaNext: Anand Kumria
Message 3 of 4 in “On boolean configuration variables...”
  1. Junio C HamanoJun 24, 2006
  2. Anand KumriaJun 25, 2006
  3. Johannes SchindelinJun 25, 2006
  4. Anand KumriaJun 25, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.