Expandable Functional Markup
- Both expandable and already expanded.
Currently in development. Please do not use yet as it may cause issues with certain things not working as expected or not there at all.
See the Todo list for a list of things that have been implemented for each compiler logic.
A lot of the logic bit of the compiler logic is taken from Build a programming language from scratch by Tylerlaceby and modified. This is because I have never programmed a compiler or anything like this before and thought it would be an interesting concept to learn more.
I do not claim to have written all of the code. Some bits may be the exact same as his. He is also listed in the Credits.
Coded in TypeScript using Deno.
Credits | Todo list | Documentation for the formats | Examples / Syntax-guide
XFM tries to bridge the gap between:
- Existing programming langauges (like JavaScript, Typescript, C and Python)
- Making websites simpler to make (without html so things like coding the website in the backend at the same time as coding the backend)
- Styling (like tailwindcss and markdown)
XFM uses multiple different file-types for different things (like JavaScript does with ESModules and CommonJS being seperate). These file-types are:
- Style (
.xfms- Compiles to CSS, Markdown or HTML and the user can choose which one to compile to) - Logic (
.xfml- Compiles to JavaScript) - Website (
.xfmw- Compiles to HTML with a mix of CSS and JS as well)
Each different file-type has:
- The same compiler and CLI tool called XFMC.
- A similar but different syntax that should be decently easy to use for experienced people.
- Compatibility between different file-types so people can use one type in a different type.
- Semi-compatibility with existing programming languages: Python, JS ESModules, TS and CSS.
- Ability to be used on their own with external things like XFM - style compiled to CSS with HTML or XFM - logic to runnable JS code using NodeJS or Deno to run it.
The inner-workings of the compiler is basically 3 compilers mixed together for use together in a single executable or package (coming soon; for NPM, PNPM, Yarn). They all have their own seperate logic and work seperately but can call each other using the main code bit or CLI.
Note
No file-types have been implemented yet. Please wait until further commits for any use at all.
Because of the different file-types for different things, you will need a specific file-type for the specific documentation you want to read.
-
If you want the Style documentation then go to the formats/STYLE.md file.
-
If you want the Logic documentation then go to the formats/LOGIC.md file.
-
If you want the Website documentation then go to the formats/WEBSITE.md file.
Note
Not all documentation has been written yet. At the moment (25th of April 2025), only progress on logic has been made.
- If you want the Logic syntax examples then go to the logic.xfml file or the logic syntax-guide.
Note
Not all syntax examples have been written yet. At the moment (25th of April 2025), only progress on logic has been made.