[dev-context] Fwd: Re: Definition of \doframedparentparameter

[Hans Hagen]

-------- Original Message --------
Subject: Re: Definition of \doframedparentparameter
Date: Mon, 28 May 2012 19:38:27 +0200
From: Hans Hagen <pragma at wxs.nl>
To: Marco <netuse at lavabit.com>

On 28-5-2012 19:30, Marco wrote:
> On 2012-05-28 Hans Hagen<pragma at wxs.nl>  wrote:
>
>>> \def\doframedparentparameter#1#2{\ifx#1\relax\doframedrootparameter#2\else\doframedparameter#1{#2}\fi}
>
>
>> normally #1 is a \cs and helpers like \doframedparentparameter are not
>> user commands
>
> I was talking about the second argument #2. If #2 is always a
> command, then you can write
>
> \def\doframedparentparameter#1#2{\ifx#1\relax\doframedrootparameter#2\else\doframedparameter#1#2\fi}
>
> if not, then
>
> \def\doframedparentparameter#1#2{\ifx#1\relax\doframedrootparameter{#2}\else\doframedparameter#1{#2}\fi}
>
> but the actual definition is neither of them, that is what confused me.

Users can do \setupframed[mine:whatever=wewant] and then say
\framedparameter{mine:whatever}. They never see or use the #1 (being a
special and abstract namespace value). It's the value of \currentframed
that starts the lookup chain.  Also, a lot of this low level code is
optimized for performance.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------