easyjevko.lua
queryjevko.js
easyjevko.lua | queryjevko.js | |
---|---|---|
5 | 2 | |
0 | 0 | |
- | - | |
10.0 | 10.0 | |
over 1 year ago | over 1 year ago | |
Lua | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
easyjevko.lua
-
Jevko: a minimal general-purpose syntax
Now if you take the simplest possible format built on Jevko, e.g. https://github.com/jevko/easyjevko.lua which specifies the conversion of jevkos to Lua tables and strings then an empty jevko is always converted to an empty string. Empty tables or nulls are simply prohibited in this format.
queryjevko.js
-
Jevko: a minimal general-purpose syntax
The grammar of S-exps on the other hand, I won't quote here, but I assure you it's much more complicated. How much depends on your flavor (Jevko is also simpler in this regard: there is only one flavor, clearly specified).
There is no (intended) ambiguity around whitespace in Jevko: whitespace does not occur explicitly in the grammar. Whitespace characters are just characters. This is the defining feature of the syntax.
For this reason Jevko is more low-level: if you want to treat whitespace in some special way, you have to do that yourself. Although for most use-cases this is very similar and simple, e.g. https://news.ycombinator.com/item?id=33334314
But the point is that you can also leave it as-is, e.g.: https://github.com/jevko/queryjevko.js
or do something else -- it's up to your format.
-
Syntax Design
Thank you. :)
> I wonder if I should use it for something...
I'd be honored!
A couple of ideas:
How about a simple configuration format? https://gist.github.com/djedr/681e0199859874b3324eaa84192c42... (I should make a library out of this)
Or you can put it in your query strings to make them more humane: https://github.com/jevko/queryjevko.js
Or make up a markup DSL: https://github.com/jevko/markup-experiments#asttohtmltable
Or serialize game objects in your indie game. Or make it the interface of your experimental app. Or use it to shave off a few unnecessary characters off your data: https://jevko.github.io/compactness.html
No parser in your favorite language? A basic one should be only a couple dozen lines!
What are some alternatives?
jevkalk - A Jevko-based interpreter.
tree - A Data Modeling Programming Language
binary-experiments - Experiments with various binary formats based on Jevko.
algebralang - at this time this is some example code of a language I want to build
markup-experiments - A collection of experiments with Jevko and text markup.
tutorials - Tutorials related to Jevko
yapl - YAml Programming Language
specifications - Specifications related to Jevko.
FileToCArray - Coverts any file to a C style array. (It can also do image color format and size coversion)
jevko
writing - A public place for unpolished technical writing.