Ticket #671 (closed defect: wontfix)
Precedences the wrong way around
| Reported by: | uholzer | Owned by: | dmisev |
|---|---|---|---|
| Priority: | major | Milestone: | Release v1.3.0 |
| Component: | [SI] NTN | Version: | |
| Keywords: | Cc: | kohlhase, clange | |
| Blocked By: | Blocking: | ||
| Due to close: | YYYY/MM/DD | Include in GanttChart: | no |
| Dependencies: | Due to assign: | YYYY/MM/DD |
Description
According to the MKM08 paper about notations, a lower precedence means "binds stronger". (That is, if I understand that correctly, when the output precedence is smaller than the input precedence, no brackets are added.) Christoph Lange told me that the precedences are interpreted as in Prolog, where a smaller precedence means "binds stronger" as well.
JOMDoc however currently (revision 2057) does it the other way around (at least for MathML). I attached a test case which contains its own notation definitions. What JOMDoc produces is (below shown as ASCII instead of the real MathML output)
(ax) + b a + xb
but I expect
ax + b (a + x)b
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

