Inconsistent hex literals in pos:

[JKAnderson]

Starting a pos: expression with a hex literal gives very undesirable results. For instance:

instances:
  compressed:
    io: _root._io
    pos: 0x44 + _parent.compression_header_size + offset
    size: size

Generates code:

io.Seek(19332502143299584);

Placing the literal in the middle or at the end behaves as expected:

instances:
  compressed:
    io: _root._io
    pos: _parent.compression_header_size + offset + 0x44
    size: size

Generated code:

io.Seek(((M_Parent.CompressionHeaderSize + Offset) + 68));

[GreyCat]

I suspect that it's only for JavaScript version of ksc, running in IDE? JVM-based version doesn't seem to exhibit this behavior?

If yes, the problem is with the JS YAML parser (which is not really something we can fix without writing our own parser), and I believe I've seen that bug filed in the past, I'll try to find the reference now.

The simple workaround is just use quotes around the expression to clearly state that it's a string, not a hex number.

[FireyFly]

If there isn't one already, probably at least a bug should be filed upstream? And possibly other alternative yaml libraries could be looked into--three should be a few for JS probably.

[KOLANICH]

And possibly other alternative yaml libraries could be looked into--three should be a few for JS probably.

See #229

[JKAnderson]

Correct, using the web IDE.