Updating expressions in try/catch
Bug #991088 reported by
Christian Gruen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
Fix Released
|
High
|
Markos Zaharioudakis |
Bug Description
I believe that the following two expressions should raise XUST0001:
try { 1 } catch * { delete node <a/> },
try { delete node <a/> } catch * { 1 }
Source:
http://
Hope this helps,
Christian
Changed in zorba: | |
assignee: | nobody → Markos Zaharioudakis (markos-za) |
importance: | Undecided → High |
Changed in zorba: | |
milestone: | none → 2.7 |
Changed in zorba: | |
status: | In Progress → Fix Committed |
Changed in zorba: | |
milestone: | 2.7 → 2.6 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I have a pending fix for this. However, the XUST0001 error will be raised only if scripting is disabled. This is the same behaviour as for the comma operator.