A small concatenative stack-based dynamically-typed interpreted scripting language.
The main purpose of this language is to be an alternative to CSS in an highly anticipated upcoming JavaScript Framework, which will revolutionize the Web as we know it by exposing the, still untouched, performance of modern web browsers.
Not really. It's just another side-project of mine. I wanted to have a second attempt at creating a programming language.
It can be found at docs/LANGUAGE.
If you want to enable Syntax Highlighting and add support for the LSP Server on VSCode for the Pulsar Language, you can download and package the official extension found at Marco4413/vscode-pulsar-language.
None!
Except for the pulsar-demo and pulsar-tools projects
which use fmt for pretty printing.
And the pulsar-lsp project which uses lsp-framework.
The Language itself has no dependencies except for the C++20 standard library.
This project uses premake5 as its build system.
Run premake5 --arch=amd64 vs2022 to create solution files for VS.
NOTE: Run premake5 --help to get a list of available architectures.
I sometimes test Pulsar on ARM64 so it should also compile to that just fine.
Alternatively premake5 gmake2 will create Makefiles.
C++20 is the standard used by the project.
Supported compilers are gcc and msvc.
Compiler Versions:
- gcc 13.3.0
- msvc from vs2022
clang should also work but it's not my go-to compiler,
so it may break between commits.
pulsar-lsp should have no issues building. However, if you're using a
C++ LSP Server on your editor, you may notice that some header files are missing.
That happens because lsp-framework generates some header files from a json file,
which means that you must build lsp-framework before editing files from pulsar-lsp.
Building with Make:
$ make -j lspframeworkOn Visual Studio use the solution explorer to build the lspframework project.
They're within the examples folder.
The new pulsar-tools project is the preferred way of running examples.
In fact, it's the CLI tool for Pulsar.
See the Building section.
After building pulsar-tools, you'll be able to run it with no arguments to
print its usage. The default settings are the ones used for the examples.
TL;DR: After building pulsar-tools, you'll be able to:
$ pulsar-tools run path/to/pulsar/file.plsIf an example requires external arguments, just append them to the command.
There's a fully working demo within the pulsar-demo project.
You can check out the premake5.lua script and the source code within src/pulsar-demo