From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: expansion and \processaction
Date: Thu, 7 Jun 2012 17:34:38 +0200 [thread overview]
Message-ID: <20120607153438.GB4444@phlegethon> (raw)
In-Reply-To: <512FF611-2B42-42FA-8539-8D3F8585E687@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4384 bytes --]
Hi Wolfgang!
···<date: 2012-06-07, Thursday>···<from: Wolfgang Schuster>···
>
> Am 07.06.2012 um 14:05 schrieb Philipp Gesang:
>
> > Hi all,
> >
> > my goal is a macro \definestates[foo][...,...] which takes a comma
> > list and creates a monadic macro \foo[n]. \foo[n] should return
> > either the nth item or, if (n > list length), a default. I
> > thought the right tools were \processcommalist to generate the
> > mapping n-><list item>, as well as \processaction to retrieve the
> > items. But naively I didn’t consider expansion ...
> >
> > My code so far:
> >
> > ··8<····································································
> > \unprotect
> >
> > \def\definestates{\dodoubleempty\do_define_states}
> >
> > \def\do_define_states[#1][#2]{%
> > \expandafter\edef\csname#1_states\endcsname{%
> > \nstates0
> > %% this is supposed to be expanded so we employ the \raw... variety
> > \rawprocesscommalist[#2]\add_one_state%
> > unknown=>\dummystate,%
> > default=>\dummystate,%
> > }%
> > \do_do_define_states{#1}%
> > }
> >
> > \let\dummystate\empty
> >
> > \newcount\nstates
> > \unexpanded\def\add_one_state#1{%
> > \advance\nstates\plusone
> > \the\nstates=>#1,%
> > }
> >
> > \def\do_do_define_states#1{%
> > \expandafter\def\csname#1\endcsname
> > {\expandafter\dosingleempty\csname do_#1\endcsname}%
> > \expandafter\def\csname do_#1\endcsname[##1]{%
> > \iffirstargument
> > % <[DBG] cmd:#1, state:##1>\par
> > \edef\currentstates{\csname#1_states\endcsname}%
> > %% At this point \currentstates should yield the whole mapping so
> > %% we can use it with \processaction. But ...
> > % \show\currentstates
> > % \currentstates\par
> > %% ... here it still contains
> > %% \nstates 0 \rawprocesscommalist [foo,bar,baz] ...
> > %% and the next directive has an empty result:
> > \rawprocessaction[##1][\currentstates]%
> > \fi
> > }%
> > }
> >
> > \protect
> > \starttext
> >
> > \definestates[mystates][foo,bar,baz]
> > %% At this point I’d like \mystates_states to contain (literally)
> > %% “1=>foo,2=>bar,3=>baz,unknown=>,default=>,”
> > %% so the following command
> > \mystates[1] % -> foo
> > %% would be equivalent to
> > %% \processaction[1][1=>foo,2=>bar,3=>baz,unknown=>,default=>,]
> > \mystates[2] % -> bar
> > \mystates[42] % -> dummy
> >
> > \stoptext
> > ··8<····································································
> >
> > My question: How can I use \[raw]processcommalist in an expanded
> > definition? How can I get \[raw]processcommalist to operate on
> > the expansion of its second argument? Does this even make sense?
> > If not, what is the proper way?
>
> \unprotect
>
> \unexpanded\def\definestates
> {\dodoubleargument\definestates_indeed}
>
> \def\definestates_indeed[#1][#2]%
> {\setuevalue{#1}{\states_entry[#2]}}
>
> \unexpanded\def\states_entry
> {\dodoubleargument\states_entry_indeed}
>
> \def\states_entry_indeed[#1][#2]%
> {\getcommalistsize[#1]%
> \ifnum#2>\commalistsize
> {\tttf NO ENTRY!}%
> \else
> \getfromcommalist[#1][#2]\commalistelement
> \fi}
Thanks very much. This solves my problem. Very convenient that I
can rewrite it to use commacommand.
Philipp
>
> \protect
>
> \starttext
>
> \definestates[mystates][foo,bar,baz]
>
> \starttabulate
> \NC 2 \EQ \mystates [2] \NC\NR
> \NC 42 \EQ \mystates[42] \NC\NR
> \stoptabulate
>
> \stoptext
>
> Wolfgang
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-06-07 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 12:05 Philipp Gesang
2012-06-07 12:32 ` Wolfgang Schuster
2012-06-07 15:34 ` Philipp Gesang [this message]
2012-06-07 16:02 ` Wolfgang Schuster
2012-06-07 16:16 ` Hans Hagen
2012-06-07 16:55 ` Wolfgang Schuster
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=20120607153438.GB4444@phlegethon \
--to=gesang@stud.uni-heidelberg.de \
--cc=ntg-context@ntg.nl \
/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).