From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setvalue/setvariable
Date: Thu, 5 Feb 2009 22:08:38 +0100 [thread overview]
Message-ID: <F8AD1C1E-FBA3-476E-9A9C-99DEFF3BD0D4@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0902052151560.13399@gaston.couberia.bzh>
Am 05.02.2009 um 21:55 schrieb Peter Münster:
> On Thu, 5 Feb 2009, Wolfgang Schuster wrote:
>
>> A faster version of your macro is:
>>
>> \def\MyFunction
>> {\dosingleempty\doMyFunction}
>>
>> \def\doMyFunction[#1]%
>> {\removeunwantedspaces\executeifdefined{myfunction:#1}
>> {\getvalue{myfunction:default}}}
>>
>> \setvalue{myfunction:1}{\medspace dog }
>> \setvalue{myfunction:2}{\medspace cat }
>> \setvalue{myfunction:default}{\ldots}
>
> Hello,
>
> I'm working now a lot with \setvariable and \getvariable. What are the
> advantages/disadvantages of set/get-value over set/get-variable?
It's more a style decision, set/getvariable is at a higher level
than set/getvalue (just wrapper around \csname ... \endcsname) and
they provide a few test macros (doifelsevariable, doifvariable and
doifnotvariable).
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-05 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 20:26 Remove leading spaces Bart C. Wise
2009-02-05 20:36 ` Wolfgang Schuster
2009-02-05 20:50 ` Bart Wise
2009-02-05 20:55 ` setvalue/setvariable (was: Re: Remove leading spaces) Peter Münster
2009-02-05 21:08 ` Wolfgang Schuster [this message]
2009-02-05 21:37 ` setvalue/setvariable 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=F8AD1C1E-FBA3-476E-9A9C-99DEFF3BD0D4@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--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).