You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to updateeo-parser library in the jeo-maven-plugin to 0.42.0 version and got the following exception:
Invalid content was found starting with element 'comments'
For the XMIR (excerpt):
<program>
....
<objects>
....
</objects>
<comments>
<commentline="4">This is the default 64+ symbols comment in front of named abstract object.</comment>
<commentline="26">This is the default 64+ symbols comment in front of named abstract object.</comment>
<commentline="44">This is the default 64+ symbols comment in front of named abstract object.</comment>
</comments>
</program>
This XMIR was received after the following modifications:
Disassemble Java bytecode to XMIR
Translate XMIR to PHI
Translate PHI back to XMIR ( unphi)
Then I get this XMIR, convert it to EO new Xmir.Default(this.canonical).toEO(), then parse it again new EoSyntax(this.name, new InputOf(eoprog)).parsed();
And on the (4) step I get the exception, I showed above. Expected behaviour: when we transform XMIR to EO and back it shouldn't produce errors.
The text was updated successfully, but these errors were encountered:
@volodya-lombrozo probably you used an old version of XSD. Are you sure you don't have your own copy of it and uses just eo-parser package with the XSD inside?
I'm trying to update
eo-parser
library in thejeo-maven-plugin
to0.42.0
version and got the following exception:For the XMIR (excerpt):
This XMIR was received after the following modifications:
XMIR
XMIR
toPHI
PHI
back toXMIR
(unphi
)XMIR
, convert it to EOnew Xmir.Default(this.canonical).toEO()
, then parse it againnew EoSyntax(this.name, new InputOf(eoprog)).parsed();
And on the (4) step I get the exception, I showed above.
Expected behaviour: when we transform XMIR to EO and back it shouldn't produce errors.
The text was updated successfully, but these errors were encountered: