git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Dmitry Potapov" <dpotapov@gmail.com>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
	"Joshua Juran" <jjuran@gmail.com>,
	"Giovanni Funchal" <gafunchal@gmail.com>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH v2] correct verify_path for Windows
Date: Sun, 12 Oct 2008 00:58:52 +0200	[thread overview]
Message-ID: <81b0412b0810111558vb69be00if4842fa91d777c3b@mail.gmail.com> (raw)
In-Reply-To: <20081011163310.GZ21650@dpotapov.dyndns.org>

2008/10/11 Dmitry Potapov <dpotapov@gmail.com>:
>> > +   /* On Windows, file names are case-insensitive */
>> > +   case 'G':
>> > +           if ((rest[1]|0x20) != 'i')
>> > +                   break;
>> > +           if ((rest[2]|0x20) != 't')
>> > +                   break;
>>
>> We have tolower().
>
> I am aware of that, but I am not sure what we gain by using it. It seems
> it makes only code bigger and slow.

It does? Care to look into git-compat-util.h?

> ... As to readability, I don't see much
> improvement... Isn't obvious what this code does, especially with the
> above comment?

You want to seriously argue that "a | 0x20" is as readable as "tolower(a)"?
For the years to come? With a person who does not even know what ASCII is?
Ok, I'm exaggerating. But the point is: it is not us who will be
reading the code.
And even if they do this just to remove Windows quirks it is well worth to
use a bit more of english language so that they don't need a second look.
As to comment: it is just additional info. It can't be checked by compiler
if you make and accidental typo in your code (like, for example, accidentally
putting an extra pipe in that expression, should happen to that emacs users
from time to time).

BTW, is it such a critical path? Can't the code be unified and do
without #ifdef?

  reply	other threads:[~2008-10-11 23:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 14:02 Files with colons under Cygwin Giovanni Funchal
2008-10-04 23:39 ` Dmitry Potapov
2008-10-05  9:04   ` Alex Riesen
2008-10-05  9:14   ` Alex Riesen
2008-10-05 19:51     ` Dmitry Potapov
2008-10-05  9:28   ` Giovanni Funchal
2008-10-06  6:54   ` Johannes Sixt
2008-10-07  0:53     ` Dmitry Potapov
2008-10-07  6:13       ` Johannes Sixt
2008-10-07  2:05   ` Joshua Juran
2008-10-07  3:26     ` [PATCH v2] correct verify_path for Windows Dmitry Potapov
2008-10-07  6:18       ` Johannes Sixt
2008-10-11 16:33         ` Dmitry Potapov
2008-10-11 22:58           ` Alex Riesen [this message]
2008-10-12 13:50             ` Dmitry Potapov
2008-10-12 18:18               ` Alex Riesen
2008-10-13  6:00                 ` Johannes Sixt
2008-10-13  6:18                   ` Alex Riesen
2008-10-07  6:25       ` Alex Riesen

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=81b0412b0810111558vb69be00if4842fa91d777c3b@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=dpotapov@gmail.com \
    --cc=gafunchal@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=jjuran@gmail.com \
    --cc=spearce@spearce.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).