From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Yao Zhao <zhaox383@umn.edu>,
mhagger@alum.mit.edu, peff@peff.net, git@vger.kernel.org
Subject: Re: [GSOC 2014]idea:Git Configuration API Improvement
Date: Thu, 20 Mar 2014 10:36:20 -0700 [thread overview]
Message-ID: <xmqqbnx0zsa3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpqd2hh5j7k.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 20 Mar 2014 10:10:23 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Why?
>
> (In general, explaining why you chose something is more important than
> explaining what you chose)
Good educational comment. Thanks.
> A tree (AST, Abstract syntax tree) can be interesting if you have some
> source-to-source transformations to do on the configuration files (i.e.
> edit the config files themselves).
>
> For read-only accesses, I would find it more natural to have a
> data-structure that reflects the configuration variables themselves, not
> the way they appear in the config file.
... and one important thing that was left unsaid is that the
read-only accesses happen far more often than updates, so the data
structure must be optimized for the read-only look-up case.
next prev parent reply other threads:[~2014-03-20 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 7:23 [GSOC 2014]idea:Git Configuration API Improvement Yao Zhao
2014-03-20 8:47 ` Michael Haggerty
2014-03-20 9:10 ` Matthieu Moy
2014-03-20 17:36 ` Junio C Hamano [this message]
2014-03-20 21:15 ` Yao Zhao
2014-03-21 8:23 ` Matthieu Moy
[not found] ` <CAP4BmmHAuWYgeMvk11ywJ5eXQunCWPepGEE3UTKfiVn60RQVrw@mail.gmail.com>
2014-03-21 13:42 ` Matthieu Moy
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=xmqqbnx0zsa3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=zhaox383@umn.edu \
/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.