-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
enhancementNew feature or requestNew feature or request
Description
This is what I see in XMIR generated by jeo:disassemble:
<o name="j$Foo">
<o base="Q.org.eolang.string" name="base">
<o base="Q.org.eolang.bytes">
<o>51-2E-6A-65-6F-2E-63-6C-61-73-73</o>
</o>
</o>
<o base="Q.org.eolang.number" name="version">
<o base="Q.org.eolang.bytes">
<o>40-50-40-00-00-00-00-00</o>
</o>
</o>
<o base="Q.org.eolang.number" name="access">
<o base="Q.org.eolang.bytes">
<o>40-40-80-00-00-00-00-00</o>
</o>
</o>
<o base="Q.org.eolang.string" name="supername">
<o base="Q.org.eolang.bytes">
<o>6A-61-76-61-2F-6C-61-6E-67-2F-4F-62-6A-65-63-74</o>
</o>
</o>
Attributes (base, version, access, supername, and others) are not sorted. The order of them is important for phi-calculus. I suggest we introduce some ordering, which will be consistently preserved in future versions of JEO.
After #1172, the @ attribute must/will stay first.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request