simplelanguage
edn
simplelanguage | edn | |
---|---|---|
6 | 34 | |
594 | 2,567 | |
0.8% | 0.7% | |
4.8 | 0.0 | |
7 months ago | over 2 years ago | |
Java | ||
Universal Permissive License v1.0 | - |
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.
simplelanguage
-
Dada, an Experiement by the Creators of Rust
That sort of stuff is easy to do with Truffle (which, ironically, lets you define a language using what they call the "truffle dsl").
The SimpleLanguage tutorial language has a bigint style number scheme with efficient optimization:
https://github.com/graalvm/simplelanguage/blob/master/langua...
-
Apple releases Pkl – onfiguration as code language
Truffle has no opinion on how you parse the sources. It cares about how you execute them from an intermediate Truffle guided representation produced by the parser.
In other words antlr and truffle are a great fit. We even use this pairing for our example language simplelanguage.
https://github.com/graalvm/simplelanguage
- PL Scaffolding project?
- Ask HN: Recommendation for general purpose JIT compiler
-
GraalVM 22.1: Developer experience improvements, Apple Silicon builds, and more
Do you have any feedback on how we could improve the docs? If so, please let us know!
I believe the easiest way to start a new Truffle language implementation is to fork SimpleLanguage [1] and turn it into your language. Did you try to do that?
[1] https://github.com/graalvm/simplelanguage
-
Where would you recommend starting if I want to make my own programming language?
Finally, I would suggest you to take a look at the Truffle/GraalVM ecosystem(https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/). The documentation is not exactly very elaborate, but a few good resources are Mumbler(http://cesquivias.github.io/blog/2014/10/13/writing-a-language-in-truffle-part-1-a-simple-slow-interpreter/#mumbler-language), SimpleLanguage(https://github.com/graalvm/simplelanguage), and (https://www.endoflineblog.com/graal-truffle-tutorial-part-4-parsing-and-the-trufflelanguage-class).
edn
-
Apple releases Pkl – onfiguration as code language
> was utterly surprised how no one ever apparently has thought to create a configuration/templating system that's basically a fancy library on top of Scheme.
There's Clojure's extensible data notation: https://github.com/edn-format/edn
- Why the fuck are we templating YAML? (2019)
-
I made a basic python client and ORM for XTDB
A thin language layer around edn/datalog, the query language
-
What Is Wrong with TOML?
EDN (Extensible Data Notation) is a subset of Clojure: https://github.com/edn-format/edn
It is:
- Streamable
- Extensible
- Whitespace-insensitive, but there are formatting conventions for readability
-
The real reason JSON has no comments
To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.
-
Ron: Rusty Object Notation
Alien is not a reason something is bad, just that's it's unusual. JSON was a bit alien when it first arrived as well, as everyone was used to XML at the time.
`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.
Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.
-
JSON vs. XML with Douglas Crockford
I just checked out the spec, and it gets pretty ugly in the Table section. A lot of the json examples are both shorter and IMO more precise. Stuff that’s not allowed with [table] is allowed with [[table]], and it’s confusing to understand what level of depth I’m at.
I’ll take edn over any of “em. https://github.com/edn-format/edn
-
Taming the Time: how to install & develop with XTDB
As XT is written in Clojure and it natively supports Clojure’s data types, we were not satisfied with available JSON types and decided to give EDN a try - that way we would have way more supported types:
-
Design patterns are a solution to the problem OOP itself creates
Compare the nightmare that is pickling with how simple it is to serialize pure data with edn in clojure. What ends up happening is people passing around JSONs or whatever and writing parsing/encoding code at each end, which makes things unnecessarily more complex, and dangerous, and error prone, and boring, etc...
- The YAML Document from Hell
What are some alternatives?
graalvm-kotlin-native-image-sample - Example project showing how to build a native, static executable from a Kotlin project using GraalVM
json - JSON for Modern C++
Som - Parser, code model, navigable browser and VM for the SOM Smalltalk dialect
EPOE-Forked - Github repository for EPOE-Forked
minivm - A VM That is Dynamic and Fast
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
yamllint - A linter for YAML files.
clj-kondo - Static analyzer and linter for Clojure code that sparks joy
dhall-lang - Maintainable configuration files
mir - A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR
json - A tested JSON parser / serializer