ehmry
/
preserves-nim
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
Nim implementation of the Preserves data language
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
135 Commits
8 Branches
15 Tags
902 KiB
 
Branch: trunk
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'trunk'
${ noResults }
Emery Hemingway 8c0af37694
Use set[T] rather than HashSet[T] for enum sets 		4 weeks ago
src Use set[T] rather than HashSet[T] for enum sets 4 weeks ago
tests Remove old imports of parse module 5 months ago
.gitignore Schemas: use canonical meta-schema 11 months ago
.gitmodules Remove submodule 7 months ago
README.md Update upstream URLs 4 months ago
UNLICENSE Unlicense 1 year ago
preserves.nimble Use set[T] rather than HashSet[T] for enum sets 4 weeks ago
schema.bin Remove submodule 7 months ago
schema.prs Remove submodule 7 months ago

README.md

Preserves

Nim implementation of the Preserves data language.

Library

To parse or produce Preserves one should write a schema and generate a Nim module using the preserves_schema_nim utility. This module will contain Nim types corresponding to schema definitions. The toPreserve andfromPreserve routines will convert Nim types to and from Preserves. The decodePreserves, parsePreserves, encode, and $ routines will convert Preserve objects to and from binary and textual encoding.

To debug the toPreserves and fromPreserves routines compile with -d:tracePreserves.

Utilities

  • preserves_schema_nim
  • preserves_encode
  • preserves_decode
  • preserves_from_json
  • preserves_to_json

Installation

preserves_encode is a multi-call binary that implements preserves_encode, preserves_decode, preserves_from_json, and preserves_to_json, so the appropriate symlinks should be created during packaging.