From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Sixt <J.Sixt@eudaptics.com>
Subject: Re: [PATCH 3/3] Teach 'diff' about 'nodiff' attribute.
Date: Fri, 13 Apr 2007 12:30:38 +0100 [thread overview]
Message-ID: <200704131230.41594.andyparkins@gmail.com> (raw)
In-Reply-To: <461F602C.E9803108@eudaptics.com>
On Friday 2007, April 13, Johannes Sixt wrote:
> -- Hannes "Can't we not have no double negation please?" Sixt
There's nothing wrong with double negatives per se. They often confer
more meaning than simple logic would suggest.
For example:
I can't not hate CVS
I hate CVS
Logically identical, but semantically different. In the first, the
speak would be suggesting that they've tried, but failed, to like CVS;
in the second the speaker just hates it. Language isn't logic, it's
fuzzy logic :-).
The reason I think it's relevant to bring this up is that I think
identifier naming in programming should try to use language to lead the
reader down the same thought path as the writer.
You want a flag that controls whether a thread is running - should it be
called RunFlag or StopFlag?
while( RunFlag )
while( !StopFlag )
I think that the context is important.
I, personally, wouldn't like to say which is correct in that case - or
in the "nodiff"/"!diff" question. However, I don't think it's correct
to universally rule out all double negative use - they have their
place.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-13 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 9:01 [PATCH 3/3] Teach 'diff' about 'nodiff' attribute Junio C Hamano
2007-04-13 10:49 ` Johannes Sixt
2007-04-13 11:30 ` Andy Parkins [this message]
2007-04-13 11:45 ` Johannes Sixt
2007-04-13 12:54 ` Andy Parkins
2007-04-13 14:09 ` Nicolas Pitre
2007-04-13 14:26 ` Julian Phillips
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704131230.41594.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox