crow.tree VS make-link-text.js

These datatype implementations are currently stored in the wolf repo (the "stdlib"). In addition, a high-level Rails-like framework is planned to be in the crow repo. This separation is here so on the one-hand the "stdlib" is minimal, while the framework is robust and all-inclusive. For an example of some code, check out for instance this first pass at a dynamic array, here is a small snippet.

I have a basic parser to convert the Link text into a JSON tree. I had a rough draft of a basic prototype compiler here, but in the process of porting that over to BaseLink. That last link converts Link to JavaScript in a hello-world level of degree haha, didn't get anywhere near robustness yet, I'm still a beginner too. Also haven't gotten around to doing the typechecking portion yet either.

So LinkText is simply a hierarchical set of notes/thoughts/code/etc.. A simple parser would take the tree and parse it into term/text/code/nest nodes. It is then up to you to figure out what they mean.

It's nothing fancy, just an indentation-based note-taking scheme for defining specifications or even writing code. It's parsing/handling is no more sophisticated than a JSON parser, as it literally is just parsed into a simple "term and text tree". From that point it is up to the person to resolve how to interpret the tree. On some level, it is just like a trimmed downed cleaned up version of XML, without attributes.