kaitai_struct_java_runtime
kaitai_struct_java_runtime copied to clipboard
Kaitai Struct: runtime for Java
maybe generated code can be more flexible with usage of of InputStream instead of file path e.g. ``` Stl.fromFile(ClassPathResource("stl/bottom_shell_ONLY.stl").file.absolutePath) ``` it won't give chance to process files that comes from...
Runtime changes for https://github.com/kaitai-io/kaitai_struct_compiler/pull/288
[RandomAccessFile.read()](https://docs.oracle.com/javase/7/docs/api/java/io/RandomAccessFile.html#read(byte[])) can read fewer bytes than requested, this is not an EOF. -1 will be returned in case of EOF.
I noted, that this repository has some tests, but there is no corresponding CI task to run them
To allow developers without gpg test their changes I moved signing under a flag. Now if you need to sign artefacts you should pass `-DperformRelease=true` flag to the maven command:...
Runtime changes for https://github.com/kaitai-io/kaitai_struct_compiler/pull/197
Addresses #39 Generated module-info looks like this ```java module kaitai.struct.runtime { exports io.kaitai.struct; exports io.kaitai.struct.annotations; } ```
To do serialization, it appears you need to know the total byte length in advance to allocate a `ByteBufferKaitaiStream`. From http://doc.kaitai.io/serialization.html: > Current serialization support relies on fixed-length streams.... Therefore,...
Without a module-info for the runtime, kaitai generated code can't be used directly with jlink. A multi-release jar can be used instead of bumping the minimum version from 7.
That absolute positions must be stored in the debug maps (`_attrStart`, `_attrEnd`, `_arrStart`, `_arrEnd`). Without that it is impossible or too hard to determine correct position of parsed objects, especially...