Content-Type: text/plain; charset="UTF-8"
From: Mark Anderson <markr.anderson@amd.com>
To: Carl Worth <cworth@cworth.org>
In-Reply-To: <877hsv6hbo.fsf@yoom.home.cworth.org>
References: <20091126202347.GA16654@blackspot>
	<1260364206-344-1-git-send-email-meskio@sindominio.net>
	<20091209132446.GC23878@blackspot>
	<877hsv6hbo.fsf@yoom.home.cworth.org>
Date: Wed, 9 Dec 2009 14:21:04 -0700
Message-ID: <1260392368-sup-9167@testarossa>
User-Agent: Sup/git
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] [PATCH] Added regress option to tags iterator
Precedence: list

Excerpts from Carl Worth's message of Wed Dec 09 13:08:43 -0700 2009:
> On Wed, 9 Dec 2009 14:24:46 +0100, Ruben Pollan <meskio@sindominio.net>=
 wrote:
> > Do you like to call them regress? Should I change that?
>=20
> I don't love the name, (since it's so close to the word "regression"
> which has a totally different meaning in software context). But I also
> don't have an immediate suggestion for an improved name yet either.
>=20
> > What about the functions notmuch_*_is_first? Is kind of reversed logi=
c than
> > notmuch_*_has_more, the last are true when is not reach the limit but=
 the
> > first ones are true when the limit is reached. But I think it make se=
nse like
> > that.
>=20
> I'd like a more symmetric API here. Anyone have a favorite set of names
> for iterating a list in two directions?

I like vocabulary games:

fwd/bck
forward/reverse
next/prev
advance/retreat
inc/dec
iter_fwd/iter_back
earlier/later
younger/older

I think that changing has_more is going to be a requirement to come up wi=
th a consistent set of names.

>=20
> -Carl