LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Mon, 1 Jul 2013 18:05:22 -0400
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
Subject: Re: Defining \bool_case:nn
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=UTF-8
From: "Joel C. Salomon" <[log in to unmask]>
Parts/Attachments: text/plain (17 lines) 
On Mon, Jul 1, 2013 at 2:30 AM, Joseph Wright
<[log in to unmask]> 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’ve invited A. Ellett (the fellow who requested \bool_case on TeX.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.

—Joel

ATOM RSS1 RSS2