From: Joey McCollum via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Joey McCollum <jmccollum20140511@gmail.com>
Subject: Re: xml processing: if elseif else / switch case
Date: Thu, 9 Dec 2021 11:30:45 -0500 [thread overview]
Message-ID: <CAGxRUG9ToHGL82ddmau1ur17sUor4nd--FgXjSoywLpHxG7y5Q@mail.gmail.com> (raw)
In-Reply-To: <62b08e5c-4ef8-fd93-63ba-90095f2626e9@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 3134 bytes --]
Thanks for correcting that, Wolfgang. I must have added the other \fi
instances because I was trying to use \orelse in MKIV and couldn't get it
to work. Is it only supported in LMTX?
Joey
On Thu, Dec 9, 2021 at 11:30 AM Hans Hagen via ntg-context <
ntg-context@ntg.nl> wrote:
> On 12/9/2021 5:11 PM, Wolfgang Schuster via ntg-context wrote:
> > Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
> >> I believe \orelse might be what you want. It works with most \if...
> >> macros, and it avoids nesting of \doifelse constructs. Here's an
> >> example, which I use in conditionally removing preceding punctuation
> >> if any other keys are defined before a specific one in an assignment:
> >>
> >> ```
> >> % If any of the preceding keys was specified, then replace any
> >> preceding punctuation with a space
> >> % and typeset the number with its CSL abbreviation, followed by a
> >> comma
> >> \ifdefined\btxsbllocvol
> >> \removeunwantedspaces\removepunctuation\btxspace
> >> \orelse\ifdefined\btxsbllocno
> >> \removeunwantedspaces\removepunctuation\btxspace
> >> \fi
> >> \orelse\ifdefined\btxsbllocpt
> >> [...]
> >> \fi
> >> ```
> >
> > The \fi at the end of each \orelse branch is wrong.
> >
> > \ifdefined\btxsbllocvol
> > ...
> > \orelse\ifdefined\btxsbllocno
> > ...
> > \else
> > ...
> > \fi
> and when 'string' comparison is needed one can do:
>
> \starttext
>
> \def\foo{foo}
> \def\ofo{ofo}
> \def\oof{oof}
>
> \def\XXX{ofo}
>
> \ifcstok\XXX\foo
> FOO
> \orelse\ifcstok\XXX\ofo
> OFO
> \orelse\ifcstok\XXX\oof
> OOF
> \else
> XXX
> \fi
>
> \def\XXX{\ofo}
>
> \iftok{\XXX}{\foo}%
> FOO
> \orelse\iftok{\XXX}{\ofo}%
> OFO
> \orelse\iftok{\XXX}{\oof}%
> OOF
> \else
> XXX
> \fi
>
> \ifcstok{\XXX}\foo
> FOO
> \orelse\ifcstok{\XXX}\ofo
> OFO
> \orelse\ifcstok\XXX}\oof
> OOF
> \else
> XXX
> \fi
>
> \stoptext
>
> watch the subtle differences. It all makes coding in tex primitives a
> bit more visual appealing and readable. Oone of the objectives of lmtx
> is that users can read the context code without pondering too much about
> the syntax or getting depressed by possibly obscure helper macros and
> expansion trickery.
>
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 4615 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-12-09 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 8:19 Denis Maier via ntg-context
2021-12-09 14:08 ` Joey McCollum via ntg-context
2021-12-09 16:11 ` Wolfgang Schuster via ntg-context
2021-12-09 16:28 ` Hans Hagen via ntg-context
2021-12-09 16:30 ` Joey McCollum via ntg-context [this message]
2021-12-09 16:53 ` Hans Hagen via ntg-context
2021-12-09 17:24 ` Denis Maier via ntg-context
2021-12-09 17:32 ` Wolfgang Schuster via ntg-context
2021-12-10 10:25 ` Denis Maier via ntg-context
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=CAGxRUG9ToHGL82ddmau1ur17sUor4nd--FgXjSoywLpHxG7y5Q@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=jmccollum20140511@gmail.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).