From: normalperson at yhbt.net (Eric Wong)
Subject: Policy on global variables
Date: Thu, 16 Jan 2014 00:59:12 +0000 [thread overview]
Message-ID: <20140116005912.GA20306@dcvr.yhbt.net> (raw)
In-Reply-To: <CAHmME9rKGfPx6ppX3VtN06Cd0YpAGCuzM4WW5A-sg7i3q6ZoTg@mail.gmail.com>
"Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
> In theory, passing around the variable, and not relying on a global,
> is better. It allows us at somepoint to have multiple contexts, for,
> say, implementing FastCGI or an event loop single-process multi
> response model.
This. I prefer we keep passing around the ctx variable to keep the code
more flexible for future reuse. Of course, IIRC git itself has this
limitation, too...
next prev parent reply other threads:[~2014-01-16 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 0:06 Jason
2014-01-16 0:20 ` Jason
2014-01-16 0:59 ` normalperson [this message]
2014-01-16 1:00 ` Jason
2014-01-16 8:06 ` hjemli
2014-01-16 10:47 ` normalperson
2014-01-16 11:31 ` Jason
2014-01-16 13:08 ` john
2014-01-16 18:38 ` Jason
2014-01-16 21:21 ` john
2014-01-16 21:26 ` Jason
2014-01-16 21:34 ` john
2014-01-16 21:36 ` Jason
2014-01-16 22:20 ` john
2014-01-16 23:42 ` Jason
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=20140116005912.GA20306@dcvr.yhbt.net \
--to=cgit@lists.zx2c4.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).