| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000508 | mercury | Bug | public | 2020-05-17 01:31 | 2020-10-16 07:11 | ||||
| Reporter | juliensf | ||||||||
| Assigned To | zs | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000508: Type constructors that are also Mercury operators result in invalid .int3 files | ||||||||
| Description | Type constructors that are also Mercury operators (like rule or pragma) result in .int3 files the compiler cannot read back in. This is due to the operators not being escaped in :- type_representation items. For example, extras/moose/grammar.m contains a type named rule/0, which results in the following in the .int3 file :- type_representation(grammar.rule, is_word_aligned_ptr) Currently, extras/moose and samples/muz cannot being compiled with the current ROTD. (Also, why does the first argument of the type_representation item need to be module qualified?) | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-05-17 01:31 | juliensf | New Issue | |
| 2020-05-17 03:06 | zs | Assigned To | => zs |
| 2020-05-17 03:06 | zs | Status | new => assigned |
| 2020-10-16 07:11 | zs | Status | assigned => resolved |
| 2020-10-16 07:11 | zs | Resolution | open => fixed |
| 2020-10-16 07:11 | zs | Note Added: 0001120 | |
| Issue History |