EByte 0.6.0 adds three kinds of field and finishes a Windows gap. Floats come in 32 and 64 bits, and every bit pattern round-trips, NaN payloads and negative zero included. Bit fields pack small numbers into shared bytes and can drive lengths and conditions like any integer. A byte field can now run up to an offset another field declares, which covers the gap between a header and the data it points to. And --output FILE now works on Windows with the same rule as elsewhere: create a new file, never replace one. CI tests Windows on every push.
The case study tried each new field on a different format. Halving every sample of a float WAV in the JSON took its peak from -6 to -12 dB in ffmpeg, and a NaN with a custom payload came back bit for bit. An 8-bit BMP’s palette, read up to the declared pixel offset, had one colour changed from red to orange with one byte of change, which Pillow confirmed. An IPv4 header’s packed version, length and flag bits decoded to the same values dpkt reports. The schema library gained the float WAV and 8-bit BMP schemas.
An independent review found nothing blocking. Its small items were fixed before the release: an out-of-range literal offset is now refused when the schema loads, and Windows refuses names that would write into a hidden stream of another file. Binaries for Linux, macOS and Windows are on the latest release, open source under Apache 2.0.