91 lines
2.3 KiB
Markdown
Raw Normal View History

2023-10-17 09:06:14 +00:00
# q
A simple programming language.
2023-10-17 13:10:35 +00:00
## Features
2023-10-21 15:46:20 +00:00
* Fast compilation
* Small binaries
2023-10-17 13:10:35 +00:00
2023-10-17 09:06:14 +00:00
## Installation
```shell
git clone https://git.akyoto.dev/cli/q
cd q
go build
```
2023-10-17 13:10:35 +00:00
## Usage
2023-10-17 09:06:14 +00:00
2023-10-21 15:46:20 +00:00
Build a Linux ELF executable from `examples/hello`:
2023-10-17 13:10:35 +00:00
```shell
2023-10-17 18:29:36 +00:00
./q build examples/hello
2023-10-23 10:37:20 +00:00
./examples/hello/hello
2023-10-17 13:10:35 +00:00
```
2023-10-17 09:06:14 +00:00
2023-10-28 10:51:19 +00:00
## Documentation
2023-10-23 10:37:20 +00:00
2023-10-28 10:51:19 +00:00
### [main.go](main.go)
2023-10-28 11:02:26 +00:00
Entry point. It simply calls `cli.Main` which we can use for testing.
2023-10-28 10:51:19 +00:00
### [src/cli/Main.go](src/cli/Main.go)
The command line interface expects a command like `build` as the first argument.
Commands are implemented as functions in the [src/cli](src/cli) directory.
Each command has its own set of parameters.
### [src/cli/Build.go](src/cli/Build.go)
The build command creates a new `Build` instance with the given directory and calls the `Run` method.
If no directory is specified, it will use the current directory.
If the `--dry` flag is specified, it will perform all tasks except the final write to disk.
This flag should be used in most tests and benchmarks to avoid needless disk writes.
```shell
q build
q build examples/hello
q build examples/hello --dry
```
### [src/build/Build.go](src/build/Build.go)
The `Build` type defines all the information needed to start building an executable file.
The name of the executable will be equal to the name of the build directory.
2024-06-02 13:20:05 +00:00
`Run` starts the build which will scan all `.q` source files in the build directory.
Every source file is scanned in its own goroutine for performance reasons.
Parallelization here is possible because the order of code in a directory is not significant.
The main function is meanwhile waiting for new function objects to arrive from the scanners.
Once a function has arrived, it will create another goroutine for the function compilation.
The function will then be translated to generic assembler instructions.
All the functions that are required to run the program will be added to the final assembler.
2023-10-28 10:51:19 +00:00
The final assembler resolves label addresses, optimizes the performance and generates the specific x86-64 machine code from the generic instruction set.
The `Run` method is currently not fully implemented.
2023-10-23 10:37:20 +00:00
## Tests
2023-10-21 15:46:20 +00:00
```shell
2023-10-23 10:37:20 +00:00
go test -coverpkg=./...
```
## Benchmarks
```shell
go test -bench=. -benchmem
2023-10-21 15:46:20 +00:00
```
2023-10-17 09:06:14 +00:00
## License
Please see the [license documentation](https://akyoto.dev/license).
## Copyright
© 2023 Eduard Urbach