LEPTRIS

Documentation

Pick your surface

One C99 core — libleptris v1.9.156 — behind the leptris Ruby gem (v1.9.156.0), the leptris package for Python, and a pipe-friendly CLI. These guides are curated; the repositories are canonical.

guide

01Getting started — C →

Build, install, and link libleptris from source or vcpkg.

guide

02Ruby →

The leptris gem — Nokogiri-compatible parsing, XPath, SAX, C14N.

guide

03Python →

The leptris package via cffi — parse, navigate, query, serialize.

guide

04CLI →

leptris parse · xpath · format — man pages and completions.

guide

05XPath 1.0 →

All 13 axes, 27 functions, 15 operators — W3C-conformant.

guide

06Internals & FFI →

Memory model, ABI stability, the binding contract.

guide

07Parsing models →

DOM, SAX, StAX-style pull, iterparse — when to pick each.

guide

08Teptris — getting started (C) →

Build libteptris, install it via CMake or pkg-config, parse and emit TOML from C.

guide

09Teptris — Ruby →

The teptris gem — tomlib-shaped TOML with Time/Date datetimes, batch, lazy, schema plans.

guide

10Teptris — Python →

The teptris package — tomllib-shaped loads/dumps, abi3 wheels, batch and lazy paths.

guide

11Teptris — JavaScript/TypeScript →

The teptris npm package — WebAssembly TOML with first-class types, no fallback.

guide

12Teptris — Rust →

The teptris crate — hand-maintained FFI over the C engine, 7-45x the toml crate on loads.

guide

13Yeptris — getting started (C) →

Build libyeptris, install it via CMake or pkg-config, parse and emit YAML from C.

guide

14Yeptris — Ruby →

The yeptris gem — Psych-compatible YAML, strict JSON, Document node API, platform gems.

guide

15Yeptris — Python →

The yeptris package — PyYAML-shaped safe_load/safe_dump, ctypes FFI, no compilation.

reference

07Changelog →

Releases of the C library and the Ruby gem, with canonical links.

the race

09Benchmarks →

Per-language detail: libxml2 and pugixml in C/C++; Nokogiri, Ox, Oga in Ruby; the Python field.

canonical

08Repo docs →

README, guides, FFI design, validation notes — in the source tree.