New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

p:catch order #597

Closed
xml-project opened this Issue Oct 31, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@xml-project
Contributor

xml-project commented Oct 31, 2018

Currently the specs say:

Each p:catch pipeline is considered in document order.

and

It is a static error (err:XS0064) if the code attribute is missing from any but the last p:catch or if any error code is repeated.

Because no code can be repeated, I do not see why implementations are restricted to consider p:catch-elements in document order (and how this can be tested).

Proposal: Remove the restriction "document order".

@gimsieke

This comment has been minimized.

Contributor

gimsieke commented Oct 31, 2018

If the codes can’t repeat on p:catch and no more than one error can be thrown at a time, I think this constraint can indeed be dropped.

@ndw

This comment has been minimized.

Contributor

ndw commented Nov 1, 2018

👍

@xml-project

This comment has been minimized.

Contributor

xml-project commented Nov 3, 2018

Fixed with pr #621

@xml-project xml-project closed this Nov 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment