a project where I abuse CC and hexcasting circles (+ ducky peripherals to tie them together)
to achieve what can only be describes as "some" storage

so re-build pattern registry run node util/buildreg.js
to compile a hexpattern into a json run node util/parsehex.js <hexpattern> [out.json]
so to compile circle.hexpattern you would
node util/parsehex.js circle.hexpattern circle.json
you can then drop hex.lua into a cc machine along with the circle.json
and then in cc run hex load circle.json
this will write circle.json to the first focal port it can connect to

note: currently parsehex messes with number patterns (by doing a intro/retro/flock disnt.)
so if you are indexing into your source code... it may get a bit messy


notes about hexpattern format

• <Iota>: direct insertion, no escape
  
• <{Iota}>: embed with intro/retro/flock
  
• <\Iota>: embed with consideration(s)
  
• <<Iota>>: embed with intro or considerations, whichever is shorter
  

currently you can use json for iotas thatdont have a pre-handled parser
types with # are json and do not have a shorthand current types that can be parsed

• #Numbers (decimal and not)
• #Strings ("quoted strings")
• #Booleans (true/false (case sensitive))
• Vector3 ((x,y,z) format, could use json {"x":0,"y":0,"z":0} format also if you wish)
• list of iotas [iota,iota2,iota3]
• Null (null or {"null":true})
• Garbage ({"garbage":true} (json), or garbage (not case sensitive))