MIME-Version: 1.0
References: <CAFUtaNGAO6gsaGNv8nrDug6VMuZFZaarWtk5Nr-f7DAn0_tWYg@mail.gmail.com>
            <51D121F7.9050308@morningstar2.co.uk>
Content-Type: text/plain; charset=UTF-8
Message-ID:  <CAFUtaNEFu1PzGbe=W2=zbuwB3F2KT6cwnkNan+CckrNEcMf3sQ@mail.gmail.com>
Date:         Mon, 1 Jul 2013 18:05:22 -0400
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: "Joel C. Salomon" <joelcsalomon@GMAIL.COM>
Subject: Re: Defining \bool_case:nn
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <51D121F7.9050308@morningstar2.co.uk>
Precedence: list
Content-Transfer-Encoding: quoted-printable
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On Mon, Jul 1, 2013 at 2:30 AM, Joseph Wright
<joseph.wright@morningstar2.co.uk> wrote:
> I'm not sure I see the need for this. In the other 'case' functions, at
> most exactly one case can be true
<snip>
> However, in \bool_case:nn you stop at the first case that happens to be
> true. That means that order matters for the result, which isn't what
> happens in the other case functions.

I=E2=80=99ve invited A. Ellett (the fellow who requested \bool_case on Te=
X.SE)
to join this thread and explain, but my guess would be that he's got a
group of booleans, only one of which is supposed to be set at any
given time: a selection from a set of mutually-exclusive options, for
example.

=E2=80=94Joel