Re: Option syntax

/ Jeni Tennison <jeni@jenitennison.com> was heard to say:
[...]
| I understand the argument that it'd be a pain for implementers to
| provide context to all XPath expressions while still providing
| efficient applications, but given a choice between least surprise to
| users and least work to implementers, I'm going to opt for the former.
| In all other cases (eg <p:for-each>, <p:viewport>, <p:choose>), we say
| that the default readable port provides the context if one isn't
| specified explicitly.

Yes. I've never thought of options in these terms, but I concede that
the principle of least surprise applies.

| In the case of <p:choose> (where you also have
| to evaluate an XPath expression), it's a dynamic error if the default
| readable port gives a sequence: if you prefer that rule to picking the
| first document, I'd be happy with that.

Yes, I like that better.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | The voice of the intellect is a soft
http://nwalsh.com/            | one, but it does not rest until it has
                              | gained a hearing.-- Freud