From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jim Meyering <jim@meyering.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Don't ignore write failure from git-diff, git-log, etc.
Date: Sat, 26 May 2007 23:03:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.99.0705262243530.3366@xanadu.home> (raw)
In-Reply-To: <7vk5uvjy0g.fsf@assigned-by-dhcp.cox.net>
On Sat, 26 May 2007, Junio C Hamano wrote:
> Once you learn to _visualize_ the ordering relationship in "X op
> Y" by relying on "op" being always < or <=, you will get the
> "number line" pop in your head whenever you see a comparision
> expression, without even having to think about it, and you "see"
> X and Y on the number line:
>
> ... -2 -1 0 1 2 ...
> ---------+---------+---------+---------+---------+---------
> true: 0 <= fcntl(...)
>
>
> ... -2 -1 0 1 2 ...
> ---------+---------+---------+---------+---------+---------
> false: (0 <= fcntl(...))
>
> What the comparison is doing comes naturally to you, without
> even having to translate it back to human language "X is larger
> (or smaller) than this constant". The ordering is right there,
> in front of your eyes, before you vocalize it.
Well... it probably depends on how your brain is wired up.
I completely agree with your reasoning. It _should_ indeed be natural
and more obvious to always put things in increasing order.
BUT it is not how my brain is connected, and after many attempts I just
cannot work efficiently with your method. It simply doesn't come out
logical for me and I have to spend an unusual amount of time on every
occasion I encounter this structure to really get it. To me it always
looks backward.
And I suspect the majority of people who just cannot train their brain
with the arguably superior representation are many, probably the
majority. It appears to be the case for Linus. It is definitely the
case for me.
Nicolas, who apologizes for his defective brain.
next prev parent reply other threads:[~2007-05-27 3:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 11:45 [PATCH] Don't ignore write failure from git-diff, git-log, etc Jim Meyering
2007-05-26 16:18 ` Linus Torvalds
2007-05-26 17:27 ` Junio C Hamano
2007-05-27 3:03 ` Nicolas Pitre [this message]
2007-05-27 9:16 ` Jim Meyering
2007-05-27 16:17 ` Linus Torvalds
2007-05-28 13:14 ` Jim Meyering
2007-05-28 15:46 ` Marco Roeland
2007-05-28 18:19 ` Jim Meyering
2007-05-28 19:05 ` Marco Roeland
2007-05-28 20:23 ` Jim Meyering
2007-05-28 23:41 ` Petr Baudis
2007-05-28 20:44 ` Junio C Hamano
2007-05-29 20:11 ` Jim Meyering
2007-05-29 23:50 ` Junio C Hamano
2007-05-30 7:12 ` Jim Meyering
2007-05-28 16:32 ` Linus Torvalds
2007-05-28 20:04 ` Jim Meyering
2007-05-29 3:01 ` Linus Torvalds
2007-05-29 20:19 ` Jim Meyering
2007-05-29 21:19 ` Linus Torvalds
2007-05-30 12:25 ` Jim Meyering
2007-05-30 15:40 ` Linus Torvalds
2007-05-30 16:12 ` Jim Meyering
2007-05-28 21:27 ` Junio C Hamano
2007-05-29 3:47 ` Linus Torvalds
2007-05-30 11:39 ` Jim Meyering
2007-05-30 17:51 ` Junio C Hamano
2007-05-30 19:43 ` Jim Meyering
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=alpine.LFD.0.99.0705262243530.3366@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).