- From: Norman Walsh <ndw@nwalsh.com>
- Date: Wed, 31 Aug 2011 11:32:31 -0400
- To: XProc Dev <xproc-dev@w3.org>
- Message-ID: <m2wrdty4ts.fsf@nwalsh.com>
Florent Georges <fgeorges@fgeorges.org> writes: > Yes, thanks. Btw the error message Calabash gives is > "empty-option.xproc:7:27:err:XD0023:Undeclared variable in XPath > expression: $opt". Maybe the "undeclared" is not exactly right. Fair enough. >>> 3/ if I evaluate it passing any non-zero-length string for >>> $opt, then the output would be <when/> > >> No. The result depends on the effective boolean value of the >> string. So 'false' and possibly other values (I don't recall >> the EBV rules for string off the top of my head) would give you >> <otherwise/>. > > Yes, I simplified a bit for the sake of conciseness. But > nontheless, whatever string I pass (with an EBV of true()), I get > always <otherwise/> instead of <when/>, except with the exact > strings "true" and "1". Weird... Very. Can you give an example of a string that has an EBV of true that Calabash interpretes as "false"? Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation Phone: +1 413 624 6676 www.marklogic.com
Received on Wednesday, 31 August 2011 15:33:13 UTC