Petr Pučil
Petr Pučil
In https://github.com/kaitai-io/kaitai_struct/issues/1019#issuecomment-1503799161, I mentioned that you should be able to qualify a type reference with the name of the top-level ("root") type: ```ksy meta: id: nested_types_paths seq: - id: obj_a...
The integer division operation currently doesn't behave the same way in all languages, if the quotient (division result) is a negative number. Here's a summary table (`-20 / 12 =...
Since 0.9, KSC doesn't generate any validation for a positional instance which uses the `contents` key: ```ksy meta: id: contents_fail_inst instances: e: pos: 0 contents: [0xc8] ``` In this case,...
There is an informal standard described at https://no-color.org/ aimed at command-line programs that produce color output by default to respect the `NO_COLOR` environment variable to disable default color output. It...
See https://github.com/kaitai-io/kaitai_struct_webide/pull/166#discussion_r1478183200 (cc @GreyCat) https://github.com/kaitai-io/kaitai_struct_webide/issues/165 discusses switching to [js-yaml](https://github.com/nodeca/js-yaml) from yaml.js that we had been using. This was addressed in https://github.com/kaitai-io/kaitai_struct_webide/pull/166. However, there are still two usages of [yaml.js](https://github.com/jeremyfa/yaml.js) left...
See https://github.com/kaitai-io/kaitai_struct_webide/pull/166#discussion_r1478180065 (cc @GreyCat) When adding the [`js-yaml`](https://www.npmjs.com/package/js-yaml) dependency in https://github.com/kaitai-io/kaitai_struct_webide/pull/166, I couldn't use the TypeScript definitions available [in the DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/acfda2eda280d0f1520af7478ea3e02d1b825fb2/types/js-yaml/index.d.ts) repo directly, because they use `unknown`. The `unknown` type...
Currently, `ksv`'s usage help looks like this: ```console $ ksv --help Usage: ksv [options] ...| ``` Note the ellipsis in `...`, indicating that multiple .ksy files are accepted. Indeed, `ksv`...
I was wondering how it is possible that the `EnumImport` test passes in Ruby (see https://ci.kaitai.io/ or [`ci.json:239-243`](https://github.com/kaitai-io/ci_artifacts/blob/3aa03d081786114ed075f74c9d8f211a6617020d/test_out/ruby/ci.json#L239-L243) of the `ruby/3.3-linux-x86_64` target). The [`enum_import.ksy`](https://github.com/kaitai-io/kaitai_struct_tests/blob/f7bfcf9989d7667e50f4a209a46e93c968b326eb/formats/enum_import.ksy) spec imports two other .ksy specs...
I would like to additionally mention something I just recognized in my use case, because I have 4 types in 2 KSY files currently using each other: Type1.ksy -> Type1.1...
Related: - https://github.com/kaitai-io/kaitai_struct/issues/393 - https://github.com/kaitai-io/kaitai_struct_compiler/pull/254 - https://github.com/kaitai-io/kaitai_struct/issues/1051 Cc @GreyCat In https://github.com/kaitai-io/kaitai_struct_compiler/pull/254, a precompile step `CanonicalizeEncodingNames` was added. It validates every `encoding` YAML key, issues a warning if it specifies a...