Open yegor256 opened 1 day ago
I see this code in XMIR generated by jeo:disassemble:
jeo:disassemble
[...] <metas> <meta> <head>package</head> <tail>j$org.j$eolang.j$benchmark</tail> <part>j$org.j$eolang.j$benchmark</part> </meta> <meta> <head>alias</head> <tail>jeo.opcode</tail> <part>jeo.opcode</part> </meta> <meta> <head>alias</head> <tail>jeo.label</tail> <part>jeo.label</part> </meta> </metas> <objects> <o abstract="" name="j$Big"> <o base="jeo.int" line="643600858" name="version"><!-- 52 --> <o base="org.eolang.bytes" data="bytes">00 00 00 00 00 00 00 34</o> </o> [...]
Here, the jeo.int in the @base attribute doesn't mean Q.jeo.int, but instead it means j$Big.jeo.int. In order to mean Q.jeo.int it must be mentioned in the alias, just like it's done with the jeo.label. All jeo.* objects must have their aliases.
jeo.int
@base
Q.jeo.int
j$Big.jeo.int
jeo.label
jeo.*
@volodya-lombrozo please, check
@yegor256 the puzzle #890 is still not solved.
@yegor256 This one should be solved in the 0.6.20 version.
0.6.20
I see this code in XMIR generated by
jeo:disassemble
:Here, the
jeo.int
in the@base
attribute doesn't meanQ.jeo.int
, but instead it meansj$Big.jeo.int
. In order to meanQ.jeo.int
it must be mentioned in the alias, just like it's done with thejeo.label
. Alljeo.*
objects must have their aliases.