W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

Re: Parameters and options

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Mon, 16 Apr 2007 13:41:58 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87mz18nrmh.fsf@nwalsh.com>
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say:
| Norman Walsh writes:
|>   <px:debug>
|>     <p:parameter name="elemcountplus1" select="$elemcount+1"/>
|>     <p:parameter name="elemcount" select="count(//*)">
|>       <p:pipe step="loader" port="result"/>
|>     </p:parameter>
|>   </px:debug>
|> And it's up to implementations to make sure that parameters get
|> evaluated in the right order and that there are no circular
|> dependencies. (In this case, elemcount=1 and elemcountplus1=2.)
| Not at all.  There is previous mail about this (previous thread starts
| [1]).  In that thread I proposed the unordered, step-scoped parameter
| binding approach:
|  "The environment which the p:import-parameter should use clearly does
|  _not_ create a loop, and the XPath should be seeing the same
|  environment."
| and you agreed.

Right. Brain cramp. I'd just written the code to sort out step orders
so I had in mind writing the code to sort out parameter orders. :-)

I'm just as happy not to have to.

| Also, in that thread, and in the spec., we agreed that _only_
| parameters are available for $ reference, so even if the above were
| allowed, it would mean that option opt2 has value 4.

That works for me too.

                                        Be seeing you,

Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.

Received on Monday, 16 April 2007 17:42:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC