W3C home > Mailing lists > Public > xproc-dev@w3.org > May 2009

Re: Detecting unbound options

From: mozer <xmlizer@gmail.com>
Date: Thu, 28 May 2009 09:58:14 +0200
Message-ID: <21d9ade60905280058l441fb084t51257ad45968cead@mail.gmail.com>
To: Toman_Vojtech@emc.com
Cc: xproc-dev@w3.org
On Thu, May 28, 2009 at 9:42 AM,  <Toman_Vojtech@emc.com> wrote:
>> But I, again, voice for the suggestion
>>
>> > 2) To add an attribute on p:with-option that says
>> > @bound-like-this-option="$foo" ; if foo is bound then the variable
>> > will be bound and the value will be the content of the
>> select and will
>> > not be bound if $foo isn't bound
>>
>> We could also add for more complex use case the
>> p:is-option-bound() function
>
> So what about the case when the select expression refers to multiple
> options/variables (some/all of which can be unbound)?

That's what I called a "complex use case" where you cannot avoid using p:choose.

Xmlizer
Received on Thursday, 28 May 2009 07:58:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 May 2009 07:58:51 GMT