Skip to content

Perimortem 0.3.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 01 Oct 23:13
· 59 commits to main since this release

Perimortem 0.3.0 packages the core runtime and utility library as static and shared SDKs, with component interfaces for Core, Utility, Math, Memory, Compression, Serialization, and System.

Changes since 0.1.0:

  • Build and package through Toolchain 0.3.0. Public headers live under source/perimortem, matching their include paths. Root build declarations use the shared library, package, tests, benchmarks, and vscode helpers.
  • Ship static and shared libraries for Linux, Windows, and WebAssembly. The compiled API and supported stream template instantiations have explicit exports. Windows archives distinguish the static library from the DLL import library.
  • Select component interfaces without exposing every Perimortem header. Components share the runtime while retaining their declared public header dependencies.
  • Remove the former TTX ABI adapters, Core::Object, Core::Implementation, descriptor binding, and the legacy Terminal wrapper. Perimortem's runtime no longer supplies those TTX-specific object and terminal interfaces.
  • Simplify Dynamic::Bytes and Dynamic::Record around direct storage. Bytes copies own independent storage, and writable access no longer triggers copy-on-write machinery. Remove the obsolete map laundering operation.
  • Separate geometry and storage from rendering: Math supplies points, sizes, boundaries, domains, and volumes; Memory supplies Matrix; PNG serialization uses Rgba8 samples. Rendering belongs to Photophore.
  • Require explicit bounds when converting C strings with NullTerminated::convert_cstring. Exact-length to_view conversions preserve embedded zero bytes.
  • Keep tests and benchmarks as standalone executables with working-directory fixture paths. Shared VS Code configuration supplies separate Debug and Release workflows.

The standard repository commands are:

bazel build ...
bazel run :tests
bazel run :benchmarks
bazel build :sdk --config=release
bazel run :vscode

The SDK target is excluded from wildcard builds. Requesting :sdk packages both linkage variants for all supported platforms, together with headers, source, component metadata, and checksums.

Existing consumers should update removed object/ABI interfaces, use Core::Scalar in place of Core::Math, and select the required SDK linkage and components. C_LINKAGE from toolchain/export.h replaces PERIMORTEM_C. Static consumers need PERIMORTEM_STATIC=1; Toolchain's SDK importer supplies it automatically. Shared consumers use the default import declarations.

End-to-end Windows validation remains outstanding.