All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] add GIT_FAST_STAT mode for Cygwin
Date: Tue, 23 Sep 2008 19:51:19 +0200	[thread overview]
Message-ID: <gbbaam$hte$1@ger.gmane.org> (raw)
In-Reply-To: 20080923165247.GO21650@dpotapov.dyndns.org

Dmitry Potapov wrote:
> On Tue, Sep 23, 2008 at 04:37:14PM +0200, Alex Riesen wrote:
>> 2008/9/23 Dmitry Potapov <dpotapov@gmail.com>:

>>> +stat_fn_t cygwin_stat_fn = cygwin_stat_choice;
>>> +stat_fn_t cygwin_lstat_fn = cygwin_lstat_choice;
>> ...
>>> +typedef int (*stat_fn_t)(const char*, struct stat*);
>>> +extern stat_fn_t cygwin_stat_fn;
>>> +extern stat_fn_t cygwin_lstat_fn;
>> 
>>     extern int (*cygwin_stat_fn)(const char *, struct stat *);
>> 
>> Is shorter, easier to read and easier to understand (for a C person).
>> You don't even use the type anywhere else, it is just for the declaration sake!
> 
> I use it in description of a parameter of another function:
> 
> static int do_stat(const char *file_name, struct stat *buf, stat_fn_t cygstat)
> 
> Of course, you can avoid it here too, but the declaration will become
> somewhat longer:
> 
> static int do_stat(const char *file_name, struct stat *buf,
>        int (*cygstat)(const char *, struct stat *));
> 
> so I am not sure that removing stat_fn_t improves readability, but if
> there are other people who think so, I will correct that.

I think that using typedef here definitly improves readibility.
You don't have to carefully analyse if you can pass cygwin_stat_fn
to do_stat function or not.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2008-09-23 17:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 14:06 [PATCH] add GIT_FAST_STAT mode for Cygwin Dmitry Potapov
2008-09-23 14:37 ` Alex Riesen
2008-09-23 16:52   ` Dmitry Potapov
2008-09-23 17:51     ` Jakub Narebski [this message]
2008-09-24 11:25     ` Alex Riesen
2008-09-24 14:03       ` Dmitry Potapov
2008-09-24 14:42         ` Alex Riesen
2008-09-24 15:02           ` Shawn O. Pearce
2008-09-24 15:09             ` Alex Riesen
2008-09-24 15:16               ` Shawn O. Pearce
2008-09-24 15:32                 ` Alex Riesen
2008-09-23 15:31 ` Shawn O. Pearce
2008-09-23 17:12   ` Dmitry Potapov
2008-09-23 19:06     ` Shawn O. Pearce
2008-09-23 20:04       ` Dmitry Potapov
2008-09-23 20:17         ` Shawn O. Pearce
2008-09-23 21:28           ` Dmitry Potapov
2008-09-23 21:58             ` Shawn O. Pearce
2008-09-23 19:03 ` Johannes Sixt
2008-09-23 19:48   ` Dmitry Potapov
2008-09-23 20:41     ` Johannes Sixt
2008-09-23 21:11       ` Dmitry Potapov
2008-09-27  7:02 ` [PATCH v2] Add a "fast stat" " Marcus Griep
2008-09-27  8:35   ` Alex Riesen
2008-09-27 10:39   ` Dmitry Potapov

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='gbbaam$hte$1@ger.gmane.org' \
    --to=jnareb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.