[tools] Add S-Expression Output Type to rlparser#5943
Open
VisenDev wants to merge 2 commits into
Open
Conversation
VisenDev
changed the title
rlparserrlparser
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
S-Expressions are a simple file format that has been around since the 1950s. They consist of nested lists surrounded by parenthesis. The source code of LISP family languages like Common Lisp, Scheme, Clojure, Racket, or Emacs Lisp are represented using S-Expressions.
They are a good candidate for a raylib api output format because they are extremely simple to write a parser for, and all lisp family languages have built in functionality for parsing and manipulating S-Expressions, so they are a good choice for a data exchange format.
You could also change the file extensions and flags to
LISPinstead ofSEXPR, but I wanted to convey that the output is just data, not lisp code.I chose to only use the most basic of S-Expression syntax so that the output would be mutually parsable by different lisps. (ie no
(dotted . lists)no common lisp:keywords)