git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Heiko Voigt <hvoigt@hvoigt.net>,
	msysGit Mailinglist <msysgit@googlegroups.com>,
	Johannes Sixt <j.sixt@viscovery.net>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCHv4 1/6] environment: static list of repo-local env vars
Date: Wed, 24 Feb 2010 07:58:17 -0800	[thread overview]
Message-ID: <7vhbp64odi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1266996196-25978-2-git-send-email-giuseppe.bilotta@gmail.com

Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:

> +/* Repository-local GIT_* environment variables */
> +const char *const local_repo_env[] = {
> +	ALTERNATE_DB_ENVIRONMENT,
> +	CONFIG_ENVIRONMENT,
> +	DB_ENVIRONMENT,
> +	GIT_DIR_ENVIRONMENT,
> +	GIT_WORK_TREE_ENVIRONMENT,
> +	GRAFT_ENVIRONMENT,
> +	INDEX_ENVIRONMENT,
> +	NO_REPLACE_OBJECTS_ENVIRONMENT,
> +	NULL
> +};
> +
> +const unsigned int local_repo_env_size = ARRAY_SIZE(local_repo_env);

This does not look very useful for two reasons.

 - It counts the NULL at the tail, so the number is one-off; you cannot
   say

	for (i = 0; i < local_repo_env_size; i++)
		do_something_to(local_repo_env[i]);

 - local_repo_env_size is not a compile time constant, so you cannot do:

	const char *env[local_repo_env_size + 20];
	memcpy(env, local_repo_env, sizeof(env[0]) * local_repo_env_size);
	for (i = local_repo_env_size; i < ARRAY_SIZE(env); i++)
		add_more_to(env + i, ...);

  reply	other threads:[~2010-02-24 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  7:23 [PATCHv4 0/6] repo-local env vars handling Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 1/6] environment: static list of repo-local env vars Giuseppe Bilotta
2010-02-24 15:58   ` Junio C Hamano [this message]
2010-02-24 19:20     ` Giuseppe Bilotta
2010-02-24 19:36       ` Junio C Hamano
2010-02-24 23:11         ` Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 2/6] connect: use " Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 3/6] rev-parse: --local-env-vars option Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 4/6] shell setup: clear_local_git_env() function Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 5/6] submodules: ensure clean environment when operating in a submodule Giuseppe Bilotta
2010-02-24  7:23 ` [PATCHv4 6/6] is_submodule_modified(): clear environment properly Giuseppe Bilotta
2010-02-24  8:06   ` Johannes Sixt
2010-02-24  8:55     ` Giuseppe Bilotta
2010-02-24  9:18       ` Johannes Sixt
2010-02-24 10:07         ` Giuseppe Bilotta

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=7vhbp64odi.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=hvoigt@hvoigt.net \
    --cc=j.sixt@viscovery.net \
    --cc=msysgit@googlegroups.com \
    /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).